Franck Bui 47cf786c0a coredump: rely on /proc exclusively to get the name of the crashing process ... I couldn't see any reason why the kernel could provide COMM to the coredump handler via the core_pattern command line but could not make it available in /proc. So let's assume that this info is always available in /proc. For "backtrace" mode (when --backtrace option is passed), I assumed that the crashing process still exists at the time systemd-coredump is called. Also changing the core_pattern line is an API breakage for any users of the backtrace mode but given that systemd-coredump is installed in /usr/lib/systemd, it's a private tool which has no internal users. At least no one complained when the hostname was added to the core_pattern line (f45b801551)... Indeed it's much easier to get it from /proc since the kernel substitutes '%e' specifier with multiple strings if the process name contains spaces (!).		2019-06-26 11:17:23 +02:00
..
50-coredump.conf.in	coredump: rely on /proc exclusively to get the name of the crashing process	2019-06-26 11:17:23 +02:00
50-default.conf	sysctl: bump pid range only on 64-bit systems	2019-05-20 18:13:59 +02:00
50-pid-max.conf	sysctl: bump pid range only on 64-bit systems	2019-05-20 18:13:59 +02:00
meson.build	sysctl: bump pid range only on 64-bit systems	2019-05-20 18:13:59 +02:00