On Apr 2, 2005 10:18 PM, Suresh Ramasubramanian <[EMAIL PROTECTED]> wrote: > This patch makes cron use UTC http://widell.fulhack.nu/bd/dst/
UTC is not the solution - if I can use UTC, I'd have used it on my computer and never had this problem, right? I think a good cron implementation should: 1. During spring-forward: a) crontab should warn the user that the scheduled program will not run during the missing hour, if it detects an instance during that time. b) crond should do what the HP/UX man page you posted earlier - run it at time+1hour, with all the constraints HP puts in. 2. During fall-back: a) crontab should warn the user that the program might be run twice. b) crond should run it only once (the first time). But I do think HP's implementation has a few drawbacks. Consider this crontab: 0,45 0,3,6,9,12,15,18,21 * * * /path/to/command 30 1,4,7,10,13,16,19,22 * * * /path/to/command 15 2,5,8,11,14,17,20,23 * * * /path/to/command (ie, a command scheduled to run every 45 minutes starting at midnight) Tonight, it will run at 1:30, but the next instance, 2:15 won't be run. HP's doc assures us that the 2:15 version will be run at 3:15 - but that is AFTER the 3:00 run - ie, your entire scheduling is disrupted. If the command is run to include incremental data, you might corrupt your database. This is not the ideal solution. The HP manpage is also not clear about this situation. Binand ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-india-help mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-india-help
