tag:blogger.com,1999:blog-4670131101708278676.post8610207384652605512..comments2009-12-30T16:36:28.041-02:00Comments on Niels Horn's Blog has moved!: Flexible schedulingniels.hornhttp://www.blogger.com/profile/17580941921421597835noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4670131101708278676.post-14194359309018749542009-10-12T09:21:04.538-03:002009-10-12T09:21:04.538-03:00Thanks for the "crontips" :)
I didn'...Thanks for the "crontips" :)<br />I didn't know about the */5 use for the minutes - It makes life simpler indeed.niels.hornhttps://www.blogger.com/profile/17580941921421597835noreply@blogger.comtag:blogger.com,1999:blog-4670131101708278676.post-79568033127132021812009-10-12T04:55:34.524-03:002009-10-12T04:55:34.524-03:00Greetings, Niels.
I just think cron isn't tha...Greetings, Niels.<br /><br />I just think cron isn't that bad but, sure, a front-end would be highly appreciated by many people.<br /><br />I'm dropping in this comment just to tell you that "crontab -e" is a better way to edit your crontab: the command is shorter and it handles crontab restarting for you.<br /><br />Another "crontip": instead of adding 12 entries in order to run the same command each five minutes, you could simply use a "*/5 * * * *" instead.<br /><br />As an example, experiment adding the following line to your crontab:<br /><br />*/2 * * * * date "cron command run on: +%Y%m%d-%H:%M" >> ~/cronlog.log<br /><br />Then you go take a coffe, return and issue a "crontab -e" and comment out that line, otherwise it would fill your hard drive with test-junk. Finally, a "cat ~/cronlog.log" will show the results.<br /><br />So your crontab could look like this, instead:<br /><br /># Special 5-minute-interval job<br />*/5 * * * * /usr/local/sbin/sched5 1> /dev/null<br /><br />Have fun. :)gmbastoshttp://www.linuxquestions.org/user/gmbastos-334561/noreply@blogger.com