Software clock wierdness!
One of my linux machines seems to have a slow (software) clock.
Here follows output of really simple and hacked perl script.
Basically it open()s a pipe to the program "ssh \"while /bin/true; do date; sleep 1; done\""
Then waits and snarfs input, and sees how much time elapsed locally between lines.
The machine I ran this script on has a "correct" clock.
The hardware clock seems to be running just fine (or at least relatively fine compared).
(with a very technologically advanced (or not) "one thousand one" spoken count, the hardware clock is accurate.)
Any idea what the problem is?
Will a restart fix it, or is it something more screwey that'll take me hacking something?
Here follows output of really simple and hacked perl script.
Basically it open()s a pipe to the program "ssh
Then waits and snarfs input, and sees how much time elapsed locally between lines.
and@intra foo $ ./test.pl 30 file2 Running for 30 "seconds" (whatever comes first) Testing file2 Mon May 16 02:55:45 MDT 2005 - Mon May 16 02:22:57 MDT 2005 (1 2) Mon May 16 02:55:48 MDT 2005 - Mon May 16 02:22:58 MDT 2005 (2 5) Mon May 16 02:55:51 MDT 2005 - Mon May 16 02:22:59 MDT 2005 (3 8) Mon May 16 02:55:54 MDT 2005 - Mon May 16 02:23:00 MDT 2005 (4 11) Mon May 16 02:55:57 MDT 2005 - Mon May 16 02:23:01 MDT 2005 (5 14) Mon May 16 02:56:00 MDT 2005 - Mon May 16 02:23:02 MDT 2005 (6 17) Mon May 16 02:56:03 MDT 2005 - Mon May 16 02:23:03 MDT 2005 (7 20) Mon May 16 02:56:05 MDT 2005 - Mon May 16 02:23:04 MDT 2005 (8 22) Mon May 16 02:56:08 MDT 2005 - Mon May 16 02:23:05 MDT 2005 (9 25) Mon May 16 02:56:11 MDT 2005 - Mon May 16 02:23:06 MDT 2005 (10 28) Mon May 16 02:56:14 MDT 2005 - Mon May 16 02:23:07 MDT 2005 (11 31) dest: 11, src: 31 start: 1116233743, end: 1116233774, total: 31 Source clock is running faster then dest clock. (x2.81818)
The machine I ran this script on has a "correct" clock.
The hardware clock seems to be running just fine (or at least relatively fine compared).
file2 root # while /bin/true; do date; hwclock --show; echo; sleep 1; done Mon May 16 03:19:33 MDT 2005 Thu May 12 20:23:01 2005 -0.745759 seconds Mon May 16 03:19:34 MDT 2005 Thu May 12 20:23:04 2005 -0.236009 seconds Mon May 16 03:19:36 MDT 2005 Thu May 12 20:23:07 2005 -0.132037 seconds Mon May 16 03:19:37 MDT 2005 Thu May 12 20:23:10 2005 -0.135813 seconds Mon May 16 03:19:38 MDT 2005 Thu May 12 20:23:13 2005 -0.132556 seconds Mon May 16 03:19:39 MDT 2005 Thu May 12 20:23:16 2005 -0.263509 seconds
(with a very technologically advanced (or not) "one thousand one" spoken count, the hardware clock is accurate.)
Any idea what the problem is?
Will a restart fix it, or is it something more screwey that'll take me hacking something?
