On 3 July 2011 21:27, lee <[email protected]> wrote: > You need to figure out what happens to trigger the freezing. Are there > any entries in syslog that might indicate something? There's cron > scripts running over night ... Perhaps the easiest way to approach this > is setting the system clock 12 hours or so ahead and see if the freeze > occurs at a different time. If it does, you can try to track down what > scripts are running over night and find out which one causes the > freeze. > > Or you could try to stop the cron daemon and see if it still freezes. > > Take a look at /Documentation/sysrq.txt in the kernel source > tree. Perhaps you can get at least some info when the computer is frozen > with that.
I'll have to try sysrq key combinations. Adrian -- 24x7x365 != 24x7x52 Stupid or bad maths? <erno> hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/CABAdhH4F7aknpS5h9EH+o9hf9EoufpQ9-E7mDmiMBrd=x2r...@mail.gmail.com
