Timeline for Run systemd timer even if process is still running
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 6, 2023 at 11:27 | comment | added | Daniel Krajnik | I think so, it was necessary to install core/cron package (cronie) to run crontab -e and after removing .service and .timer units they no longer appear in the systemctl list-timers view. So I think it's cron/anacron now. | |
| Sep 6, 2023 at 8:44 | comment | added | Tripple Moon | @Daniel, AFAIK systemd does automatic crontab translation to timer units. So are you sure cron is actually performing those self or does systemd indirectly? | |
| Sep 5, 2023 at 22:00 | comment | added | Daniel Krajnik | RuntimeMaxSec makes sense until one day you have a massive backup on a slow internet connection that so just happens will take more than an hour to complete. | |
| Sep 5, 2023 at 21:59 | comment | added | Daniel Krajnik | For that reason I gave up on trying to use systemd timers for backups - it's just too unreliable. Rewrote it to a regular crontab job and it just works™. | |
| Sep 5, 2023 at 21:58 | comment | added | Daniel Krajnik | Theoretically I agree, but practically processes like restic or rclone may get stuck for whatever reason in activating state causing you to lose backups. | |
| Sep 4, 2023 at 20:31 | history | edited | Tripple Moon | CC BY-SA 4.0 | added 34 characters in body |
| Sep 4, 2023 at 20:30 | history | edited | Tripple Moon | CC BY-SA 4.0 | added 111 characters in body |
| Sep 4, 2023 at 20:26 | history | edited | Tripple Moon | CC BY-SA 4.0 | added 156 characters in body |
| Sep 4, 2023 at 20:22 | history | edited | Tripple Moon | CC BY-SA 4.0 | added 354 characters in body |
| Sep 4, 2023 at 20:08 | history | edited | Tripple Moon | CC BY-SA 4.0 | added 73 characters in body |
| Sep 4, 2023 at 20:02 | history | answered | Tripple Moon | CC BY-SA 4.0 |