Hello, I've investigated this run-away problem deeper and now have a small shell script which monitors the proc 'events/0' in the way that all 600 seconds the CPU time consumed in the last 600 seconds is compared against 2 (normally it is 0 or 1 sec, but if 'events/0' it is a big jump to some hundred);
the script can be found in http://www.unixarea.de/monEvents.sh and if the situation occurs the script monEvents.sh calls a Python script '/home/root/sys/shuttdown.py', can be found in http://www.unixarea.de/shuttdown.py which offers the user the option to re-boot (which is better than running out of battery, I think); ofc, this is only a hack and OM should fix that 'events/0' issue asap; Thx matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e <[email protected]> - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ SPAMer of the year: Subject: Alle Software ist Deutsche Sprachen >From: -40 % die Neujahrsaktion <[email protected]> _______________________________________________ Openmoko community mailing list [email protected] http://lists.openmoko.org/mailman/listinfo/community
