Timeline for Does systemd timer unit skip the next run if the process hasn't finished yet?
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2024 at 6:53 | comment | added | Sylvain | many years later, it still confusing in the doc if two tasks could overlap or not. The manpage given above, also found here: nick.groenen.me/notes/systemd-timers-dont-overlap don't offer confusion free information. If you're not well informed about systemd logic and jargon. Thanks for the clarification here in this topic. 👍️ | |
| Aug 31, 2021 at 16:03 | comment | added | AdminBee | @TomOnTime It's your reward for asking an obviously relevant question, so just enjoy as the rep keeps rolling in ;) | |
| Jun 28, 2018 at 14:17 | comment | added | rfmoz | @intelfx well, it may be better to said a restart option | |
| Jun 27, 2018 at 20:57 | comment | added | intelfx | @Rfraile then don’t make it RemainAfterExit=true? what you want is semantically contradictory. | |
| Jun 27, 2018 at 20:47 | comment | added | rfmoz | I miss an option for re-execute services with RemainAfterExit=true | |
| Oct 21, 2017 at 7:39 | comment | added | TomOnTime | @Sam That sentence is so obtuse, I foresee plenty of rep in my future. | |
| Sep 13, 2017 at 16:29 | comment | added | Sam | This is now part of the systemd docs - 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. There is no concept of spawning new service instances in this case. freedesktop.org/software/systemd/man/systemd.timer.html | |
| Aug 11, 2017 at 12:57 | comment | added | TomOnTime | I keep getting rep as people invite this. I hope systemd doesn't clarify their docs. | |
| Feb 22, 2017 at 2:25 | comment | added | intelfx | @Gima ...however, an oneshot unit that has RemainAfterExit=true will remain "active" when its initial process exits, so subsequent triggers of a timer will be ignored unless an administrator explicitly deactivates (stops) that unit, or it is brought down by negative dependencies. | |
| Feb 22, 2017 at 2:22 | comment | added | intelfx | @Gima an oneshot unit without any extra parameters is considered "activating" while its initial process is running, and becomes "inactive" when it exits. At this time, another trigger can activate that unit again. | |
| Feb 22, 2017 at 2:10 | comment | added | Gima | Could you clarify "oneshot"-services? In my view a "oneshot"-service shouldn't run another copy under any circumstances (manpage: process has to exit before systemd starts follow-up units) | |
| Aug 27, 2015 at 16:40 | vote | accept | TomOnTime | ||
| May 13, 2015 at 21:32 | history | edited | intelfx | CC BY-SA 3.0 | added 4 characters in body |
| May 13, 2015 at 21:23 | history | answered | intelfx | CC BY-SA 3.0 |