core_pattern

[Tom Horsley]

I see the systemd fungus has grown over the
/proc/sys/kernel/core_pattern file now.

Can I make it stop changing it?

Or do I have to make an rc.local script to reset it
to just plain old 'core'?

[Kevin Fenzi]

On Wed, 10 Dec 2014 12:31:50 -0500
Tom Horsley  wrote:
> I see the systemd fungus has grown over the
> /proc/sys/kernel/core_pattern file now.

This is to allow core dumps to get handled by systemd and info to go to
the journal. Abrt also overrides it to handle crashes (and has for a
long time)
> Can I make it stop changing it?

ln -sf  /usr/lib/sysctl.d/50-coredump.conf /dev/null
> Or do I have to make an rc.local script to reset it
> to just plain old 'core'?

Nope, just point the system provided 50-coredump.conf to /dev/null and
sysctl will not set it on boot.

kevin

[Tom Horsley]

On Wed, 10 Dec 2014 10:55:56 -0700
Kevin Fenzi wrote:
> Abrt also overrides it to handle crashes (and has for a
> long time)

Yea, but disabling the abrt* services made core files "normal"
previously, now it hangs around even with them disabled :-);
> > Can I make it stop changing it?
>
> ln -sf  /usr/lib/sysctl.d/50-coredump.conf /dev/null

Thanks!

[Tom Horsley]

On Wed, 10 Dec 2014 13:24:32 -0500
Tom Horsley wrote:
> > ln -sf  /usr/lib/sysctl.d/50-coredump.conf /dev/null
>
> Thanks!

Though come to think of it, shouldn't /dev/null be the 1st arg? :-).

[Kevin Fenzi]

On Wed, 10 Dec 2014 13:39:57 -0500
Tom Horsley  wrote:
> On Wed, 10 Dec 2014 13:24:32 -0500
> Tom Horsley wrote:
> > > ln -sf  /usr/lib/sysctl.d/50-coredump.conf /dev/null
> >
> > Thanks!
>
> Though come to think of it, shouldn't /dev/null be the 1st arg? :-).

Indeed it should. ;)

Sorry about that.

kevin

[Tom H]

On Wed, Dec 10, 2014 at 12:55 PM, Kevin Fenzi  wrote:
> On Wed, 10 Dec 2014 12:31:50 -0500
> Tom Horsley  wrote:
> > I see the systemd fungus has grown over the
> > /proc/sys/kernel/core_pattern file now.
> >
> > Can I make it stop changing it?
>
> ln -sf /usr/lib/sysctl.d/50-coredump.conf /dev/null

Shouldn't be "ln -s /dev/null /etc/sysctl.d/50-coredump.conf" for it
not to be overridden on systemd upgrades?

[Tom H]

On Wed, Dec 10, 2014 at 12:31 PM, Tom Horsley  wrote:
> I see the systemd fungus has grown over the
> /proc/sys/kernel/core_pattern file now.
>
> Can I make it stop changing it?
>
> Or do I have to make an rc.local script to reset it
> to just plain old 'core'?
> From rawhide so I'm not sure whether it's in F20, which, AFAIK, has systemd 216:

COREDUMP.CONF(5)
                                     coredump.conf

COREDUMP.CONF(5)

NAME
       coredump.conf - Coredump storage configuration file

SYNOPSIS
       /etc/systemd/coredump.conf

DESCRIPTION
       This file configures the behaviour of systemd-coredump, a
handler for core dumps invoked by the kernel.

OPTIONS
       All options are configured in the "[Coredump]" section:

Storage=
           Controls where to store cores. One of "none", "external",
"journal", and "both". When "none", the coredumps will be logged but
not stored permanently. When "external" (the default), cores will be
stored in
           /var/lib/systemd/coredump. When "journal", cores will be
stored in the journal and rotated following normal journal rotation
patterns. When "both", cores will be stored in both locations.

When cores are stored in the journal, they might be
compressed following journal compression settings, see
journald.conf(5). When cores are stored externally, they will be
compressed by default, see below.

Compress=
           Controls the type of compression for external storage.
Takes a boolean argument, defaults to "yes".

ProcessSizeMax=
           The maximum size in bytes of a core which will be
processed. Coredumps exceeding this size will be logged, but the
backtrace will not be generated and the core will not be stored.

ExternalSizeMax=, JournalSizeMax=
           The maximum (uncompressed) size in bytes of a core to be saved.

MaxUse=, KeepFree=
           Enforce limits on the disk space taken up by externally
stored coredumps.  MaxUse= makes sure that old coredumps are removed
as soon as the total disk space taken up by coredumps grows beyond
this limit (defaults to
           10% of the total disk size).  KeepFree= controls how much
disk space to keep free at least (defaults to 15% of the total disk
size). Note that the disk space used by coredumps might temporarily
exceed these limits
           while coredumps are processed. Note that old coredumps are
also removed based on time via systemd-tmpfiles(8).

SEE ALSO
       systemd-journald.service(8), coredumpctl(1), systemd-tmpfiles(8)

systemd 217

COREDUMP.CONF(5)