diff options
| author | Lennart Poettering <lennart@poettering.net> | 2016-02-08 23:39:40 +0100 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2016-02-10 16:09:24 +0100 |
| commit | 2f1a7412b2696ad6a8cbb38de89602adb0d7aa00 (patch) | |
| tree | 6cbc130ab237fecf5a1e8b99fafe673e3fcf4b6f /TODO | |
| parent | 888e378da2dbf4520e68a9d7e59712a3cd5a830f (diff) | |
| download | systemd-2f1a7412b2696ad6a8cbb38de89602adb0d7aa00.tar.gz | |
update TODO
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 11 |
1 files changed, 0 insertions, 11 deletions
@@ -33,8 +33,6 @@ Janitorial Clean-ups: Features: -* rework coredump tool to move actual processing into a socket activated service - * cache sd_event_now() result from before the first iteration... * remove Capabilities=, after all AmbientCapabilities= and CapabilityBoundingSet= should be enough. @@ -43,11 +41,6 @@ Features: * add systemctl stop --job-mode=triggering that follows TRIGGERED_BY deps and adds them to the same transaction -* coredump logic should use prlimit() to query RLIMIT_CORE of the dumpee and honour it - -* Add a MaxRuntimeSec= setting for service units (or units in general) to terminate units after they ran for a certain - amount of time - * Maybe add a way how users can "pin" units into memory, so that they are not subject to automatic GC? * PID1: find a way how we can reload unit file configuration for @@ -649,10 +642,6 @@ Features: * coredump: - save coredump in Windows/Mozilla minidump format - move PID 1 segfaults to /var/lib/systemd/coredump? - - make the handler check /proc/$PID/rlimits for RLIMIT_CORE, - and supress coredump if turned off. Then change RLIMIT_CORE to - infinity by default for all services. This then allows per-service - control of coredumping. * support crash reporting operation modes (https://live.gnome.org/GnomeOS/Design/Whiteboards/ProblemReporting) |