does /etc/sysctl.d/ really obeyed and does really override /etc/sysctl.conf

Reindl Harald h.reindl at
Fri Mar 16 14:30:43 UTC 2012

Am 16.03.2012 15:21, schrieb Michal Schmidt:
> Dne 16.3.2012 14:40, Michal Hlavinka napsal:
>> As I understand it, Muayyad has different problem. Right now, the
>> /etc/sysctl.conf we ship is not empty. It has several values set, one of
>> them is sysrq=0 he used in his example. No one set this is value, it's
>> just default value and yet, no package can change it by placing its file
>> in /etc/sysctl.d This would work only if sysctl.conf is empty and all
>> default configuration is moved to /etc/sysctl.d/00-systemdefault.conf
> See a related bug:

yes, but the really bug is that "sysctl.conf" is not shipped empty

it should be the global place where the admin can override ANY setting
from any other file/package and so it is correct to apply systcl.conf
as last item - as said only if it would be shipped empty

some package enables "net.ipv4.ip_forward"

if i say as admin "net.ipv4.ip_forward = 1" in sysctl.conf this
has usually a very good reason and no other random config
file has to override this or force me to deal with hopefully
high enough numbers in needed "/etc/sysctl.d/XX.config"

if "sysctl.conf" ould be empty as default we would have
excatly this behavior, and yes i am speaking from the
view of a sysadmin maintaining a lot of virtual servers
where "/etc/sysctl.conf" is distributed from a admin
machine to all other guest systems

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the devel mailing list