mirror of
https://github.com/systemd/systemd.git
synced 2024-11-05 15:21:37 +03:00
a327431bd1
With Type=notify services, EXTEND_TIMEOUT_USEC= messages will delay any startup/ runtime/shutdown timeouts. A service that hasn't timed out, i.e, start time < TimeStartSec, runtime < RuntimeMaxSec and stop time < TimeoutStopSec, may by sending EXTEND_TIMEOUT_USEC=, allow the service to continue beyond the limit for the execution phase (i.e TimeStartSec, RunTimeMaxSec and TimeoutStopSec). EXTEND_TIMEOUT_USEC= must continue to be sent (in the same way as WATCHDOG=1) within the time interval specified to continue to reprevent the timeout from occuring. Watchdog timeouts are also extended if a EXTEND_TIMEOUT_USEC is greater than the remaining time on the watchdog counter. Fixes #5868.
15 lines
603 B
Desktop File
15 lines
603 B
Desktop File
|
|
[Unit]
|
|
Description=Testsuite: EXTEND_TIMEOUT_USEC Success - extend timeout on all services
|
|
|
|
[Service]
|
|
|
|
# Normal success - startup / runtime / shutdown all take 8 seconds which is within the EXTEND_TIMEOUT_USEC=4 seconds interval
|
|
# runtime is 8+8+8 seconds. so we are relying on the EXTEND_TIMEOUT_USEC to exceed all stages, Start, Runtime and Stop.
|
|
# success occurs after 24 seconds
|
|
Type=notify
|
|
TimeoutStartSec=4
|
|
TimeoutStopSec=4
|
|
RuntimeMaxSec=4
|
|
ExecStart=/extend_timeout_test_service.sh SERVICE=success_all extend_timeout_interval=4 sleep_interval=2 start_intervals=3 run_intervals=3 stop_intervals=3
|