but this does not make sense the idea behind all .d is to allow packages to provide default (either kernel defaults or distro defaults) because the other choice is to use %post and sed eg. let's say I made a firewall package that needs to enable forwarding, it would put it in a sysctl.d what do you think ? what is the added value of having .conf overrides .d ? On Fri, Mar 16, 2012 at 2:47 PM, Lennart Poettering <mzerqung@xxxxxxxxxxx> wrote: > On Fri, 16.03.12 14:40, Muayyad AlSadi (alsadi@xxxxxxxxx) wrote: > >> hi everybody, >> >> in recent fedora releases I can see we have /etc/sysctl.d/ >> >> but does it really get evaluated >> >> eg. let's put in /etc/sysctl.d/00-ojuba-enabled-sysrq.conf >> >> kernel.sysrq = 1 >> >> and keep it 0 in /etc/sysctl.conf >> >> kernel.sysrq = 0 >> >> then reboot then type >> >> sysctl kernel.sysrq >> >> it was reported that this would yield 0 (maybe when no wifi and no >> network at all) > > /etc/sysctl.conf is interpreted after /etc/sysctl.d is. The former hence > overrides settings in the latter. > > Lennart > > -- > Lennart Poettering - Red Hat, Inc. > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
