-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a server which is using ntp to synchronise with the outside world with ntp.
My clock on my workstation seemed to get badly wrong this morning after playing a dvd with xine. It did not correct itself (I had been using ntpdate), so I installed chrony (which removed ntpdate). I manually changed the clock (using date -s) but of course it was not exactly correct. In fact, by running date in two terminal windows, one via ssh to the server, one locally I can see that the difference is approximately (+- 1 second) 42 seconds adrift. Now, 6 hours later that time is still 42 seconds out. How long does it take chrony to start relying on the server time and start correcting the clock? - -- Alan Chandler [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+hxD3uFHxcV2FFoIRAhbrAJ4gBPLeuQ0xHO5Ho/PDTMlXwKuqDACdHzSO savr1Opvt2AihG+qktSFtqw= =JGke -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
