On Saturday 10 May 2008, Amos Shapira wrote: > It's a long shot but maybe the script running exactly two minutes into > the daily cron jobs causes some interaction that breaks things? > How about disabling this script for this time of the day and see if > something is different? > Another option - try strace'ing it on its 2:02 run.
Maybe I wasn't clear enough, but 2:02 is always the time of the last log entry. I don't know exactly what time the crash is or exactly which cron job is running at that time. It could be as late as 2:04 since I have one job that runs every 2 minutes. So I don't know which job to disable. And even if I did, it wouldn't really prove anything since the next crash could be today or a month from now. Not crashing wouldn't prove that it won't happen at a later date. The same goes for the strace suggestion + I don't know if the strace would maybe change something. In any case, I've added 2 lines to each daily cron to write to a temp file at the satrt and end of each job. I'll check this file after the next crash to see which job started but didn't end. I know it's a kludge, but that's the best I could do for now. -- Shlomo Solomon http://the-solomons.net Sent by KMail (KDE 3.5.7) on LINUX Mandriva 2008.0 ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
