On Sun, May 31, 2015 at 8:16 AM, Tom Horsley <horsley1953(a)gmail.com> wrote:
On Sun, 31 May 2015 07:17:49 -0400, Tom H wrote:
> While it's true that you usually override a sysctl value with a
> variable=value pair, symlinking a conf file in "/etc/sysctl.d/" to
> "/dev/null" overrides a conf file with the same name in
> "/usr/lib/sysctl.d/" (I've just tried it) in the same way that
> symlinks to "/dev/null" in "/etc/systemd/system/",
> "/etc/systemd/network/", and "/etc/udev/rules.d/" override
> files in their corresponding libdir.
I tried it also, and it had no effect for me, the kernel core name
file was still the screwy one systemd creates.
Strange, Are you misnaming the file?
I can override a setting in "/usr/lib/sysctl.d/" using a same-named
file in "/etc/sysctl.d/" either by setting the variable to a different
value or by symlinking the file to "/dev/null".
Furthermore, from "man sysctl.d":
If the administrator wants to disable a configuration file supplied by
the vendor, the recommended way is to place a symlink to /dev/null in
the configuration directory in /etc/, with the same filename as the
vendor configuration file.