Matthew Jarvis wrote:
It's so funny you mention 5:37 as an example time... At one point I had
a cron job scheduled at 5:37 and for some reason it (usually) wouldn't
run or complete... changing to 5:34 solved the problem (at least well
enough)...
Never did find out what the heck the conflict was....
Was the cron job doing anything more than a Yes/No check? :)
Simply let your 'Yes' be 'Yes,' and your 'No,' 'No'; anything beyond
this comes from the evil one.
-- Matthew 5:37
_______________________________________________
EUGLUG mailing list
[email protected]
http://www.euglug.org/mailman/listinfo/euglug
