Hacker News Reader

Hacker News

Comment by champtar | Hacker News Reader

Full thread

champtar

You can also just use systemd timers :)

View on HN

Did not know. Thanks for sharing this. This looks mighty useful.

Is there a TUI to manage systemd-timers?

cron is a lot nicer imo. All your schedules are in one place and everyone knows how to access it.

There is a systemd command for that: systemctl list-timers

> cron is a lot nicer imo.

How, exactly ?

I've been a cron user forever, I had never heard of systemd timers until this thread.

A quick internet search shows:

    - Nice clean config in a file (instead of having to edit crontab)
    - Lots of great features that you would have to manually implement and maintain in cron (e.g. missed launches, duplicate runs, random delay, timeouts)

I mean sure, I've got bash script templates that let me solve the problem of preventing duplicate cron job running.

But having seen how easy it is to achieve the same thing with systemd timers whilst not requiring a whole lot of boilerplate code in each shell file ... why wouldn't you switch to systemd timers ? I sure will be.

The general consensus: "because it's systemd", "systemd is unstable", "systemd does too much", "systemd is non-unix".

I like systemd. It's a good clone of launchd

dcron is very lightweight and has most of those features. Dunno about random delay/timeouts, but worst case those sound like a 10 line shell script away.

https://github.com/dubiousjim/dcron

> dcron is very lightweight and has most of those features.

Hmm, let's see ...

   - Choice 1: Use what comes with my system (two choices, systemd or, if for the anti-systemd people... cron)
   - Choice 2: Install some random third-party that has not had any substancial git commits since 2014 (the 2019 commits are just admin metadata).

You can also just use systemd-cron :)

https://github.com/systemd-cron/systemd-cron

Reply on news.ycombinator.com