From 5157879b757bffce3da0a68ca207753569e8627d Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 22 Jul 2016 18:01:50 +0200 Subject: coredump: turn off coredump collection entirely after journald or PID 1 crashed Safe is safe, let's turn off the whole logic if we can, after all it is unlikely we'll be able to process further crashes in a reasonable way. --- src/coredump/coredump.c | 3 +++ 1 file changed, 3 insertions(+) (limited to 'src/coredump') diff --git a/src/coredump/coredump.c b/src/coredump/coredump.c index a75f364d2d..e5719e67c3 100644 --- a/src/coredump/coredump.c +++ b/src/coredump/coredump.c @@ -920,6 +920,9 @@ static int process_special_crash(const char *context[], int input_fd) { log_notice("Detected coredump of the journal daemon or PID 1, diverted to %s.", filename); + log_notice("Due to the special circumstances, coredump collection will now be turned off."); + (void) write_string_file("/proc/sys/kernel/core_pattern", "|/bin/false", 0); + return 0; } -- cgit v1.2.3-54-g00ecf