On Fri, 16.03.12 14:40, Muayyad AlSadi (alsadi(a)gmail.com) wrote: /etc/sysctl.conf is interpreted after /etc/sysctl.d is. The former hence overrides settings in the latter. Lennart -- Lennart Poettering - Red Hat, Inc.

On Fri, 16.03.12 14:54, Muayyad AlSadi (alsadi(a)gmail.com) wrote: If a package places a sysctl file in /etc/sysctl.d/ then you can override it with /etc/sysctl.conf, hence everything is as it should, no? This whole logic is designed so that the admin's configuration always takes precedence over vendor configuration. Which is the right thing to do. That said, note that it's probably a good idea if packages stick their sysctl files in /usr/lib/sysctl.d instead, so that that users can use /etc/sysctl.d/ to override that. /etc/sysctl.conf is read mostly for compatibility reasons only. Lennart -- Lennart Poettering - Red Hat, Inc.

yes exactly this is the case, we have sysrq=0 in /etc/sysctl.conf the admin can have higher number like 99-local.conf or move every thing in /etc/sysctl.conf to /etc/sysctl.d/00-defaults.conf and have a single line in /etc/sysctl.conf saying # you can override /etc/sysctl.d/*.conf here possible values and their defaults are found in /etc/sysctl.d/00-defaults.conf

On Fri, 2012-03-16 at 15:16 +0000, Matthew Garrett wrote: No Fedora package should do that. However I can imagine situation when sysadmin wants his own package to do it. I have to second the request to be the default /etc/sysctl.conf empty and moving the Fedora defaults to sysctl.d/00-systemdefault.conf. -- Tomas Mraz No matter how far down the wrong road you've gone, turn back. Turkish proverb

On Fri, Mar 16, 2012 at 10:57:13AM -0500, Chris Adams wrote: What happens if two packages want to set a sysctl to different values ? Dave

On Fri, Mar 16, 2012 at 10:57:13AM -0500, Chris Adams wrote: Where did I say they shouldn't? -- Matthew Garrett | mjg59(a)srcf.ucam.org

Once upon a time, Chris Adams <cmadams(a)hiwaay.net&gt; said: My appologies; I misread "sysrq" as "sysctl". -- Chris Adams <cmadams(a)hiwaay.net&gt; Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble.

On Fri, Mar 16, 2012 at 09:42:50PM +0200, Muayyad AlSadi wrote: But for a system wide change, that's insufficient. If 00-foo sets something to value A, and 99-bar sets it to B, and B < A, foo may not function correctly. This isn't an ordering problem, it's an exclusivity problem, because sysctls are system-wide, not per-package. Dave

Le Ven 16 mars 2012 21:16, Dave Jones a écrit : Fontconfig is system-wide too and fontconfig rules have many inter-rule interactions. There is no way a .d setup can handle conflicts, other that making crystal-clear what the ordering of config files is, and stating that the file with the highest order wins (and actually this is no different from a single monolithic config file since the same directive can occur multiple times there too and only one of those instances will be taken into account) -- Nicolas Mailhot

Am 16.03.2012 15:21, schrieb Michal Schmidt: 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 _________________ example: 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

On Fri, 16.03.12 14:40, Michal Hlavinka (mhlavink(a)redhat.com) wrote: Ah, hmm, I wasn't aware of that. I think ideally we'd just change the defaults in our kernel so that we ship with no default sysctl.conf file. Reconfiguring the kernel defaults all the time out-of-the-box sounds pretty suboptimal to me. (That said, if that's really not possible, and we need to keep the file, we should probaly name it /usr/lib/sysctl.d/00-systemd-default.conf or so) Lennart -- Lennart Poettering - Red Hat, Inc.

and Muayyad AlSadi responded: The setup of conf/oneBigFile + conf.d/manySmallFiles is so common (see the list of them on my system, below) that maybe there should be a convention on which one overrides which. Most of the packages using this configuration method are configured by reading oneBigFile, which then explicitly loads conf.d/*. In other cases, both configuration methods seem to be compiled in, and it is not clear which one is done first and thus possibly overridden. The override order is determined by whether the changes are before or after the conf.d/* invocation. If the conf.d/* load is in the beginning of oneBigFile's contents, the settings from the conf.d/* files are overridden. This is how sysctl.conf behaves. It makes more sense to me that files in conf.d override the main file, e.g. because they are loaded at the end of the oneBigFile. I prefer this behavior because the individual files in conf.d/ directory can be provided by optional components, which, in this scheme, don't have to touch the main config file. /etc/httpd/conf.d /etc/php.d /etc/dracut.conf.d /etc/ld.so.conf.d /etc/prelink.conf.d /etc/reader.conf.d /etc/X11/xorg.conf.d /etc/dracut.conf.d/01-dist.conf /etc/fonts/conf.d /etc/polkit-1/localauthority.conf.d /etc/polkit-1/nullbackend.conf.d /etc/reader.conf.d /etc/revisor/conf.d /etc/revisor-unity/conf.d /etc/yum/pluginconf.d /usr/share/X11/xorg.conf.d /usr/share/alsa/alsa.conf.d /usr/share/ghostscript/conf.d