Zbigniew Jędrzejewski-Szmek 73a99163a7 coredump,catalog: give better notice when a core file is truncated ... coredump had code to check if copy_bytes() hit the max_bytes limit, and refuse further processing in that case. But in 84ee096044, the return convention for copy_bytes() was changed from -EFBIG to 1 for the case when the limit is hit, so the condition check in coredump couldn't ever trigger. But it seems that *do* want to process such truncated cores [1]. So change the code to detect truncation properly, but instead of returning an error, give a nice log entry. [1] https://github.com/systemd/systemd/issues/3883#issuecomment-239106337 Should fix (or at least alleviate) #3883.		2016-09-28 23:50:29 +02:00
..
coredump-vacuum.c	build-sys: move coredump logic into subdir of its own	2016-02-10 14:32:27 +01:00
coredump-vacuum.h	build-sys: move coredump logic into subdir of its own	2016-02-10 14:32:27 +01:00
coredump.c	coredump,catalog: give better notice when a core file is truncated	2016-09-28 23:50:29 +02:00
coredump.conf	build-sys: move coredump logic into subdir of its own	2016-02-10 14:32:27 +01:00
coredumpctl.c	coredumpctl: delay the "on tty" refusal until as late as possible	2016-09-28 23:49:01 +02:00
Makefile	build-sys: move coredump logic into subdir of its own	2016-02-10 14:32:27 +01:00
stacktrace.c	tree-wide: make ++/-- usage consistent WRT spacing	2016-02-22 20:32:04 -08:00
stacktrace.h	build-sys: move coredump logic into subdir of its own	2016-02-10 14:32:27 +01:00
test-coredump-vacuum.c	build-sys: move coredump logic into subdir of its own	2016-02-10 14:32:27 +01:00