On Wed, Aug 21, 2002 at 07:15:14PM -0400, Theo Van Dinter wrote: felicity> That's about right, a quick 'while(1){grep ' 0' /proc/interrupts;sleep felicity> 1}' shows ~101 per second, with the overhead of doing the fork/grep... So let me get this straight...you are using the system clock to measure the system clock? :) I suggest writing down the value, counting five minutes with an EXTERNAL clock, such as a stopwatch, and then writing down the value again. (value2 - value1) / (60*5) should equal about 100. Of course, I don't see how a skew in the timer tick could cause the system time to change by a whole hour... There is also the possiblity of adjtime screwing up. There are syscalls related to adjusting the system clock used by NTP et. al. and I remember reading that xntpd had to keep up with changes between kernel revisions, or weird time setting issues would result. The program adjtimex may be interfering in some way. What does /sbin/adjtimex --print display? -- Charles R. Anderson <cra@wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886