Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Thursday 2007-12-06 at 00:18 -0500, Aaron Kulkis wrote:
This is precisely why NTP was invented -- it solves this
problem by obtaining time from calibrated time servers,
and also takes into account network latency. Level 0
Don't you understand that NTP can not adjust my system clock and quits?
27 Nov 15:31:56 ntpd[12905]: synchronized to 91.121...., stratum 2
27 Nov 15:38:31 ntpd[12905]: synchronized to 192.33...., stratum 2
27 Nov 15:39:25 ntpd[12905]: synchronized to 195.55...., stratum 2
27 Nov 15:39:40 ntpd[12905]: synchronized to LOCAL(0), stratum 10
27 Nov 16:22:22 ntpd[12905]: synchronized to 84.88...., stratum 2
27 Nov 16:22:22 ntpd[12905]: time correction of 1678 seconds exceeds
sanity limit (1000); set clock manually to the correct UTC time.
Or the smaller "time reset" events below:
[pruned]
Carlos,
I haven't been paying too much attention to what you have written re the
problem, what result do you get when you try setting the time manually,
as root, from the command line? You know, the old
ntpdate -u <IP-address-of-time-server>
I use ntpdate -u 203.12.160.2, as an example.
Ciao.
--
Past experience, if not forgotten, is a guide for the future.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
