On Thu, Jun 02, 2011 at 11:21:41PM -0500, Corey wrote:
> On 06/02/2011 02:00 PM, FRLinux wrote:
> >Hello,
> >
> >I am running OpenBSD 4.9 on a soekris which was in a closet for a few
> >months. NTP is slowly drifting back the time to normal but I am
> >wondering if anyone has seen this. It seems that every 5mn, the time
> >gap decreases, this is not a behavior I have seen.
> >
> >Running from the command line with "fix from startup" worked:
> >
> ># ntpd -d -v -s
> >ntp engine ready
> >reply from 193.1.193.135: offset 119.421739 delay 0.003728, next query 9s
> >set local clock to Thu Jun 2 19:56:25 IST 2011 (offset 119.421739s)
> >reply from 193.1.193.135: offset -0.000086 delay 0.003210, next query 5s
> >
> >Is that an expected behavior?
> >Jun 2 08:31:03 ice ntpd[21279]: adjusting local clock by 322.878786s
> >Jun 2 08:33:10 ice ntpd[21279]: adjusting local clock by 322.243729s
> >Jun 2 08:34:12 ice ntpd[21279]: adjusting local clock by 321.938780s
> >Jun 2 08:37:24 ice ntpd[21279]: adjusting local clock by 320.978779s
> >[...]
> >Jun 2 19:47:10 ice ntpd[24926]: adjusting local clock by 121.228150s
> >Jun 2 19:48:42 ice ntpd[18164]: adjusting local clock by 121.128741s
> >Jun 2 19:51:58 ice ntpd[18164]: adjusting local clock by 120.154673s
> >
> >Cheers,
> >Steph
> >
> Yes, on my Soekris net5501 that was out of commission for a month
> (but powered up) until I got the time to upgrade to a 4.9 snapshot.
> It did this for about 12 hours or so. Proper behavior I believe, to
> avoid confusing the system (or worse) with large clock jumps.
ntpd does not jump. It adjusts by running the clock faster or slower.
The offsets you are seeing are newly caclulated differences between
what ntpd thinks is the time and the clocks time.
-Otto
