On Wed, 2003-11-05 at 07:50, Evan Brown wrote: > So it froze again last night, could it be some cron job running and > messing stuff up? The error said something about interput not syncing and > pid was 0 and a bunch of hex values and then nothing. What the hell? It > seems to crash every night. I come in at 7:30am and its crashed during the > night, this is the 4th time its happened.
It might be helpful to pin down a time line when the crashes occur. You could create a crontab entry that puts a timestamp in a file every so often, let's say every 10 minutes. When you get back at work and the machine crashed, look at the file and you know roughly what time the crash occured which may help you to figure out what the box was doing at that particular time (check logs in /var/log to see what other activity took place around that time for example) or if a certain cronjob was run. Here's an example entry to put in /etc/crontab : */10 * * * * root date +%H:%M > /root/timestamp That command runs "date +%H:%M" which puts the current hour (%H), a colon (:) and then the current minute (%M) into the /root/timestamp file. If you want to run it every minute, change the */10 part to * It won't hurt to run it every minute, the 'date' program isn't resource intensive. If you run it every minute you'll get much better time line of course. Especially if you wait the time to observe two or more crashes and see if they occured at the same time. -- Gerard Beekmans http://www.linuxfromscratch.org http://www.beekmansworld.com /* If Linux doesn't have the solution, you have the wrong problem */
