Hacker News Reader

Comment by marbu | Hacker News Reader

This split between service file (what is going to happen exactly) and a timer file (when it's going to happen) is ok for complex use cases, but it really feels a bit silly when a single cron line would do the trick instead.

View on HN

there is cmdline shortcut for one-off ones at the very least

    systemd-run --user --unit=timer-name --on-active=60 /exec/path

will run it in 60 seconds

Nice, thanks for sharing this.

You can still use cron if you want...

Also the split allows easier debugging: one can define and run the service, check that it works, and then define a timer and test that separately.

Reply on news.ycombinator.com