> Setting up a cron job is a 1 line 10 second thing. Only if you don't care if it works or not. Or runs or not. Or don't care about dependencies. Stuff like

> Setting up a cron job is a 1 line 10 second thing. Only if you don't care if it works or not. Or runs or not. Or don't care about dependencies. Stuff like 'what will happen if the NFS server my job depends on is unavailable for the 10 minutes in which my job executes'. Is it ok for a bunch of cron jobs to hit a stale nfs share and hang and then execute all at once? If any of those things matter then you have to then orchestrate a combination of logging solutions, monitoring solutions, and a bunch of extra logic to your scripts to make sure they work. This is why it's foolish for enterprises to depend on cron for anything serious and why people use complex batch management software for critical batch. Systemd timers offers a intermediate solution built into the OS.