Files
systemd/man
Jan Klötzke bf76080180 core: let user define start-/stop-timeout behaviour
The usual behaviour when a timeout expires is to terminate/kill the
service. This is what user usually want in production systems. To debug
services that fail to start/stop (especially sporadic failures) it
might be necessary to trigger the watchdog machinery and write core
dumps, though. Likewise, it is usually just a waste of time to
gracefully stop a stuck service. Instead it might save time to go
directly into kill mode.

This commit adds two new options to services: TimeoutStartFailureMode=
and TimeoutStopFailureMode=. Both take the same values and tweak the
behavior of systemd when a start/stop timeout expires:

 * 'terminate': is the default behaviour as it has always been,
 * 'abort': triggers the watchdog machinery and will send SIGABRT
   (unless WatchdogSignal was changed) and
 * 'kill' will directly send SIGKILL.

To handle the stop failure mode in stop-post state too a new
final-watchdog state needs to be introduced.
2020-06-09 10:04:57 +02:00
..
2020-04-21 23:21:08 +02:00
2018-06-14 13:03:20 +02:00
2020-01-17 10:08:23 +01:00
2020-05-07 23:37:30 +02:00
2019-03-14 14:42:05 +01:00
2019-03-14 14:42:05 +01:00
2020-03-27 20:12:44 +01:00
2020-05-25 10:29:28 +02:00
2020-03-18 19:57:43 +01:00
2020-03-18 19:57:43 +01:00
2020-04-21 23:21:08 +02:00
2020-05-03 10:23:25 +02:00
2020-05-25 11:09:21 +02:00
2020-04-21 23:21:08 +02:00
2020-05-18 21:14:42 +02:00
2019-03-14 14:42:05 +01:00