John writes:
I reinstalled and reconfigured the xntpd 4.1.1. How can i be sure that xntpd working?
Here is the /var/log/ntp
4 Sep 13:39:07 ntpd[1820]: signal_no_reset: signal 17 had flags 4000000 4 Sep 13:39:07 ntpd[1810]: running as uid(74)/gid(65534) euid(74)/egid(65534). 4 Sep 13:42:24 ntpd[1810]: time set 0.000000 s 4 Sep 13:42:24 ntpd[1810]: synchronisation lost
There are no obvious errors, but the time set 0.000000 s is a bit strange. I would expect at least a little deviation from 0 (how likely is that your current system time is accurate within 6 decimal points to actual)? At any rate, to check that your machine can talk to the time server, you can type the following command as root: $ ntpdate -u timeserver where timeserver is the fully qualified domain name or IP number of a public time server. If this doesn't produce an error then you can assume that all is well. This command actually causes your local date/time to be adjusted to match that of the time server. The /etc/init.d/xntpd startup script actually does this for you once when your system starts, and then ntpd will keep things in sync afterwards. When I do this on my machine I get: $ ntpdate -u clock.isc.org 4 Sep 03:52:44 ntpdate[15387]: adjust time server 204.152.184.72 offset -0.000295 sec -Ti