Son of Beastie
Reaction score: 690
Reaction score: 471
I guess it might be tough to put a few spaced numbers in a text file ... for linux users! :-OYou can't tell cron "when this happens, run this job." For instance, if you want to be notified when you start to run low on disk space, or if the load on a machine is above a certain threshold. You could write scripts that check those things, and then run them frequently. But it'd be better if you could just count on the scheduler to do that for you.
There's also the less than friendly formatting to cron. When I've worked in hosting, I found plenty of cron jobs that were either running too often because the owner mis-formatted the time fields, or that didn't run as often as expected for the same reason. Back up jobs that should have been running daily were running once a month. Oops.
Awesome!A slight word of warning, you're probably going to need a lot of dependencies to build whenjobs on your own.
Reaction score: 119
Well, the "standard" cron has the limitation that it will only work correctly for a machine that is always on; if your machine is off when an event is scheduled, cron won't run it afterwards (ie. in half an hour when you power on your machine). However, this problem has been solved many years ago, and you can just use any suitable replacement for cron if you need this kind of functionality.graudeejs said:https://www.linux.com/learn/tutorials/552976-weekend-project-take-a-look-at-cron-replacement-whenjobs
The author mentions cron limitations. Can anyone enlighten me what he's talking about?
Reaction score: 156
Reaction score: 85