How do I really prevent /usr/lib/sysctl.d/50-coredump.conf

[Alchemist]

2015-05-29 16:23 GMT+03:00 Tom H <tomh0665 at gmail.com>:

> On Fri, May 29, 2015 at 8:45 AM, Tom Horsley <horsley1953 at gmail.com>
> wrote:
> >
> > In some message a while back the claim was made that
> > creating a /etc/sysctl.d/50-coredump.conf that was
> > empty would override the systemd installed
> > /usr/lib/sysctl.d/50-coredump.conf, but I can
> > state positively that doesn't work, the systemd
> > setting is still in force.
> >
> > What does work is (as root):
> >
> > rm -f /usr/lib/sysctl.d/50-coredump.conf
> >
> > but that file will come back if there is a systemd
> > update.
> >
> > So is there really a way to get the default
> > kernel core file pattern to stick around even
> > with systemd updates?
>
> How about trying a symlink of "/etc/sysctl.d/50-coredump.conf" to
> "/dev/null", systemctl-mask-style?
>

Don't use empty or nulled files. Sysctl variable names must be the same, to
override variable=value stored in /usr/lib/sysctl.d/*.





> --
> users mailing list
> users at lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20150529/b1767c2f/attachment.html>