Some reasons:
1. this script will be distributed on many servers.
We can update one input file and distribute it instead of updating crontabs.
2. we have many users with root access. Crontab entries can be removed by mistake.
3. Sometimes cron daemon has problem to start or hang.
I don't think that its a good idea to implement your own cron though it is tempting but i think you still can do the above with cron! you can have one cron common and copy this to other servers!
Mistake in crontab should not happen if you backup the cron before updating it! You can copy the cron to a file, update that file, then populate cron with the verified file!
cron daemon has problems! yes sometimes, but even with the script that you will make! it won't be much better than cron in hanging coz it would be simply a process after all!
If you just want a separate [tt]cron[/tt], then install one. Let those many root users to use their old [tt]cron[/tt] and for your tasks install [tt]fcron[/tt], [tt]mcron[/tt], [tt]anacron[/tt] or what is available for your system.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.