6 ms·
Seems like this is actually the default behaviour for a systemd timer, ha. "Note that in case the unit to activate is already active at the time the timer elap
by lathiat 9y ago
Seems like this is actually the default behaviour for a systemd timer, ha.
"Note that in case the unit to activate is already active at the time the timer elapses it is not restarted, but simply left running."
On the flip side I wonder if you can tell it to timeout and kill the service after a while, as I can equally see them getting stuck and never running again, a problem you don't have with the alternative method :-)
Ah, choices...
- rakoo 9y agoRight in the doc (https://www.freedesktop.org/software/systemd/man/systemd.unit.html# https://www.freedesktop.org/software/systemd/man/systemd.uni...): > JobTimeoutSec=, JobRunningTimeoutSec=, JobTimeoutAction=, JobTimeoutRebootArgument= > When a job for this unit is queued, a time-out JobTimeoutSec= may be configured. Similarly, JobRunningTimeoutSec= starts counting when the queued job is actually started. If either time limit is reached, the job will be cancelled