Subject: Re: ntpd oddities possibly related to sysctl change
To: Frederick Bruckman <firstname.lastname@example.org>
From: Sean Davis <email@example.com>
Date: 12/09/2003 00:42:40
On Mon, Dec 08, 2003 at 11:08:26PM -0600, Frederick Bruckman wrote:
> On Mon, 8 Dec 2003, Sean Davis wrote:
> > Andrew: if this isn't related to the sysctl changes, sorry in advance, but
> > that's the only thing changed that I can think of between the time ntpd was
> > working as it used to be, and when it was working as it is now.
> Better, or worse? "ntpd" was just updated to 4.2.0.
I'm not sure if it's problematic or not - I'm just wondering about the
'kernel time sync disabled 0041' then 'kernel time sync enabled 0001'
> > Nothing in the ntp configuration has changed since I upgraded from 1.6ZF to
> > ZG, but now I see:
> > Dec 8 21:33:26 eros ntpd: ntpd 4.2.0-r Mon Dec 8 02:22:34 EST 2003
> > (1)
> > Dec 8 21:33:26 eros ntpd: precision = 2.000 usec
> > Dec 8 21:33:26 eros ntpd: no IPv6 interfaces found
> > Dec 8 21:33:26 eros ntpd: kernel time sync status 0040
> > Dec 8 21:33:26 eros ntpd: frequency initialized -115.078 PPM from
> > /var/db/ntp.drift
> > Dec 8 21:37:45 eros ntpd: synchronized to 188.8.131.52, stratum=2
> > Dec 8 21:37:45 eros ntpd: kernel time sync disabled 0041
> > Dec 8 21:38:51 eros ntpd: kernel time sync enabled 0001
/~\ The ASCII
\ / Ribbon Campaign Sean Davis
X Against HTML aka dive
/ \ Email!