Hacker News new | ask | show | jobs
by vetinari 1489 days ago
> declarative model for configuration for... like everything.

Here I find that many people look for the wrong thing. Their idea is 'do $stuff at boot'.

However, systemd does 'do $stuff at $event', where 'boot' is one of the events in the set. They are not wrong though, we are used to cron is not a valid reason why it should not get unified.

1 comments

… but you can still just run your favorite crond, and keep doing exactly what you were before? I've still never run a cron job under systemd, and I've never hit trouble doing that. I.e., Systemd doesn't force you to use it for cron.

Although, now that I'm looking at ArchWiki's "list of reasons you might want to do this" … it checks off basically every problem with traditional cron. I might need to start using this.