diff options
author | Lennart Poettering <lennart@poettering.net> | 2014-10-28 02:17:12 +0100 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2014-10-28 02:19:55 +0100 |
commit | 4ffd29fda1a2621d8f1711ccaad723d327fef93a (patch) | |
tree | b363b1b68f7d04a4f2b41f9e060d4f31b13bab14 | |
parent | 3898b80d409ae16b049d46f883bf763417bb4c8a (diff) | |
download | systemd-4ffd29fda1a2621d8f1711ccaad723d327fef93a.tar.gz |
Update NEWS
-rw-r--r-- | NEWS | 17 |
1 files changed, 17 insertions, 0 deletions
@@ -22,6 +22,23 @@ CHANGES WITH 217: /run/systemd/user directory that was already previously supported, but is under the control of the user. + * Job timeouts (i.e. time-outs on the time a job that is + queued stays in the run queue) can now optionally result in + immediate reboot or power-off actions (JobTimeoutAction= and + JobTimeoutRebootArgument=). This is useful on ".target" + units, to limit the maximum time a target remains + undispatched in the run queue, and to trigger an emergency + operation in such a case. This is now used by default to + turn off the system if boot-up (as defined by everything in + basic.target) hangs and does not complete for at least + 15min. Also, if power-off or reboot hang for at least 30min + an immediate power-off/reboot operation is triggered. This + functionality is particularly useful to increase reliability + on embedded devices, but also on laptops which might + accidentally get powered on when carried in a backpack and + whose boot stays stuck in a hard disk encryption passphrase + question. + * systemd-logind can be configured to also handle lid switch events even when the machine is docked or multiple displays are attached (HandleLidSwitchDocked= option). |