2 ms·
On systemd systems there's an easier alternative to this. You can use the per-user systemd instance (systemctl --user) to install a .timer that activates a .ser
by geertj 11y ago
On systemd systems there's an easier alternative to this. You can use the per-user systemd instance (systemctl --user) to install a .timer that activates a .service file. If the .service is still running when the .timer next fires, it will not be started again. Systemd is pretty good at this kind of bookkeeping.
- kiallmacinnes 11y agoThis really isn't meant as piling on systemd - please don't read it that way! But, has systemd now replaced cron too?
- digi_owl 11y agoYep: http://www.freedesktop.org/software/systemd/man/systemd.timer.html http://www.freedesktop.org/software/systemd/man/systemd.time...