El día Thursday, January 15, 2009 a las 04:41:13PM +0100, Korbinian Rosenegger escribió:
> > my small script monitoring the events/0 proc is logging as well when the > > runaway occures, date and uptime: > > > > # cat runaway.log > > Wed Jan 14 01:20:04 CET 2009 > > 01:20:04 up 18:26, 0 users, load average: 0.42, 0.63, 0.49 > > Thu Jan 15 14:49:19 CET 2009 > > 14:49:19 up 18:26, 0 users, load average: 0.53, 0.76, 0.64 > > > > do you see the interesting point? the problem is uptime-driven! > > 18 * 3600 + 26 * 60 = 66360 > > Interesting, since it is only ~14 Minutes above 65536 and your script > checks about every 10 Minutes (i think). So maybe there's a unsigned int > overflow or a similar problem somewhere? I'm asking me why the uptime is exactly the same 18:26? The script is launched by hand after boot and does the check every 10 minutes, i.e. it can only detect the situation of runaway at discrete 10-minutes-points and logs the uptime; why this point was always 18:26 away from boot? 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 <matthias.ap...@oclc.org> - 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 <gabriellekel...@grungecafe.com> _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community