Files
systemd/src/shared
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-05-17 10:02:03 +02:00
2020-05-17 10:02:03 +02:00
2019-10-31 17:57:03 +09:00
2020-04-16 20:37:40 +02:00
2020-03-24 14:22:50 +01:00
2020-05-07 08:46:40 -07:00
2020-05-07 08:46:40 -07:00
2020-02-05 12:47:32 +00:00
2020-05-07 08:46:40 -07:00
2019-11-04 00:30:32 +09:00
2020-05-29 15:41:43 +02:00
2019-03-22 18:11:27 +01:00
2020-03-25 14:52:31 +01:00
2020-03-25 14:52:31 +01:00
2020-05-17 05:34:19 +02:00
2020-05-17 05:34:19 +02:00
2020-05-29 10:41:30 +02:00
2019-12-18 08:48:33 +01:00
2020-05-14 17:35:56 +02:00
2020-05-14 17:35:56 +02:00
2020-05-15 21:40:22 +02:00
2020-05-26 10:28:59 +02:00
2020-01-15 15:29:31 +01:00
2020-01-15 15:29:31 +01:00
2019-12-05 10:15:49 +01:00
2020-04-16 18:00:40 +02:00
2020-04-21 23:21:08 +02:00
2020-04-21 23:21:08 +02:00