5 Commits

Author	SHA1	Message	Date
Lennart Poettering	924453c225	units: lock down coredump service a bit ... Dissecting a coredump is possibly risky and might take a while, hence lock down the unit as much as we can.	2017-02-09 16:12:03 +01:00
Lennart Poettering	b6c7278c38	units: turn on ProtectKernelModules= for most long-running services	2017-02-09 16:12:03 +01:00
Lennart Poettering	c7fb922d62	units: switch on ProtectSystem=strict for our long running services ... Let's step up the protection a notch	2017-02-09 16:12:03 +01:00
Lennart Poettering	7f396e5f66	units: set SystemCallArchitectures=native on all our long-running services	2017-02-09 16:12:03 +01:00
Lennart Poettering	3c171f0b1e	coredump: rework coredumping logic ... This reworks the coredumping logic so that the coredump handler invoked from the kernel only collects runtime data about the crashed process, and then submits it for processing to a socket-activate coredump service, which extracts a stacktrace and writes the coredump to disk. This has a number of benefits: the disk IO and stack trace generation may take a substantial amount of resources, and hence should better be managed by PID 1, so that resource management applies. This patch uses RuntimeMaxSec=, Nice=, OOMScoreAdjust= and various sandboxing settings to ensure that the coredump handler doesn't take away unbounded resources from normally priorized processes. This logic is also nice since this makes sure the coredump processing and storage is delayed correctly until /var/systemd/coredump is mounted and writable. Fixes: #2286	2016-02-10 16:08:32 +01:00