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

2015-05-31 Thread Tom H
On Sun, May 31, 2015 at 10:05 AM, Tom Horsley wrote: > On Sun, 31 May 2015 09:51:25 -0400, Tom H wrote: >> >> Strange, Are you misnaming the file? > > I used cut&paste on the name from under /usr/lib > to make sure I didn't get it wrong :-). > > My theory is that systemd sets it manually despite >

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

2015-05-31 Thread Tom Horsley
On Sun, 31 May 2015 09:51:25 -0400 Tom H wrote: > Strange, Are you misnaming the file? I used cut&paste on the name from under /usr/lib to make sure I didn't get it wrong :-). My theory is that systemd sets it manually despite any udev rules, and the DumpCore=no setting in /etc/systemd/system.co

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

2015-05-31 Thread Tom H
On Sun, May 31, 2015 at 8:16 AM, Tom Horsley 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

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

2015-05-31 Thread Tom Horsley
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 w

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

2015-05-31 Thread Tom H
On Fri, May 29, 2015 at 9:33 AM, Alchemist wrote: > 2015-05-29 16:23 GMT+03:00 Tom H : >> On Fri, May 29, 2015 at 8:45 AM, Tom Horsley >> 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

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

2015-05-29 Thread Alchemist
2015-05-29 16:50 GMT+03:00 Tom Horsley : > On Fri, 29 May 2015 15:52:17 +0300 > Alchemist wrote: > > > Put kernel.core_pattern = "" in /etc/sysctl.conf and set DumpCore=no in > > /etc/systemd/system.conf > > That almost worked, but set the core file pattern to the literal > string "" > > kernel.co

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

2015-05-29 Thread Tom Horsley
On Fri, 29 May 2015 15:52:17 +0300 Alchemist wrote: > Put kernel.core_pattern = "" in /etc/sysctl.conf and set DumpCore=no in > /etc/systemd/system.conf That almost worked, but set the core file pattern to the literal string "" kernel.core_pattern = core worked better :-). -- users mailing lis

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

2015-05-29 Thread Alchemist
2015-05-29 16:23 GMT+03:00 Tom H : > On Fri, May 29, 2015 at 8:45 AM, Tom Horsley > 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

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

2015-05-29 Thread Tom H
On Fri, May 29, 2015 at 8:45 AM, Tom Horsley 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 s

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

2015-05-29 Thread Alchemist
2015-05-29 15:45 GMT+03:00 Tom Horsley : > 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 > sett

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

2015-05-29 Thread Tom Horsley
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):