-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 01 Apr 2003 7:50 pm, Michael West wrote: > On Mon, Mar 31, 2003 at 07:24:49AM +0100, Alan Chandler wrote: .. > > But after doing that, should chronyd bring the time as seen by date in > > synchonism with the server? Even after leaving it all night, the two > > machines are exactly 40 secs apart. ... > I have a server right now which is over 200 seconds off. I don't > know how that happened. It is righting itself at the rate of 2 > sec/hour.
I was seeing 0 secs per hour:-( I discovered the answer. The main server was running ntpd on a 24/7 basis. About 11 days ago my isp allocated me a new ip address (after 2 years of it being the same despite being dhcp allocated). As NTP is a UDP service it must have sent the source ip address in the message to the time server so it can see a reply. It was sending the old address and as a result never seeing the reply. It therefore became a stratus 16 server My workstation was configured to become a stratus 10 server from the local clock so that it could continue when the main server was available. It therefore was not trying to even synchronise between the two. - -- Alan Chandler [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+ifW3uFHxcV2FFoIRAvR8AJwNEE/QwHIkaVL7HfrHxTeQFYqKtwCeK2BD Waiob9oVpKi3yhwrYMGmF40= =h+Tn -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
