On Mon, Aug 11, 2008 at 09:32:12AM -0000, Scott Ritchie wrote:
> Without this, there's no way to have package defaults override
> unmodified system defaults; the sysctl.d folder becomes essentially
> useless.
>
>
> Perhaps a more complete fix is to make it clear that manual settings should be done somewhere other than sysctl.conf when the same setting is modified by something in sysctl.d. A sysadmin using a file like /etc/sysctl.d/zzz.sysctl.conf would guarantee that his override comes after packages. A simple comment explaining this at the top of /etc/sysctl.conf might help here.
Simpler would be to add Ubuntu defaults in /etc/sysctl.d/00-ubuntu.conf or
similar instead of /etc/sysctl.conf. Then, this could be overrided in
obvious ways both by system administrators (/etc/sysctl.conf) and by
packages (/etc/sysctl.d).
On Mon, Aug 11, 2008 at 09:32:12AM -0000, Scott Ritchie wrote: d/zzz.sysctl. conf would guarantee that his override comes after packages. A simple comment explaining this at the top of /etc/sysctl.conf might help here.
> Without this, there's no way to have package defaults override
> unmodified system defaults; the sysctl.d folder becomes essentially
> useless.
>
>
> Perhaps a more complete fix is to make it clear that manual settings should be done somewhere other than sysctl.conf when the same setting is modified by something in sysctl.d. A sysadmin using a file like /etc/sysctl.
Simpler would be to add Ubuntu defaults in /etc/sysctl. d/00-ubuntu. conf or
similar instead of /etc/sysctl.conf. Then, this could be overrided in
obvious ways both by system administrators (/etc/sysctl.conf) and by
packages (/etc/sysctl.d).
--
- mdz