Marcos Vinicius Lazarini wrote:
Gonda Brouerius van Nidek wrote:
I have read the info on ntpd several times and I think I understand the basics. I hope I have ntpd working on my dialup system with 9.1.
One of the possibilities to see if it really works should be to use ntpq -p I get the following output with this command but apart from recognizing the four addresses that I have chosen I do not understand the meaning of the output. Somebody with an explanation in plain English?
# ntpq -p remote refid st t when poll reach delay offset jitter ===================================== 202.180.0.71 .INIT. 16 u - 64 0 0.000 0.000 4000.00 my1.doubleukay. 192.6.38.127 2 u 40 64 1 1039.17 -183.26 0.002 ns01.deu.edu.tr .INIT. 16 u 49 64 0 0.000 0.000 4000.00 darkstar.sanet. 212.82.32.15 2 u 58 64 1 908.414 -82.537 0.002
1st step: Check if you can talk to the server: laza@nics:~> ntpdate -v -q -u time.windows.com 1 Sep 19:39:49: ntpdate 4.1.1@1.786 Thu Oct 2 20:27:36 UTC 2003 (1) server 207.46.130.100, stratum 2, offset -0.008529, delay 0.23824 1 Sep 19:39:50: adjust time server 207.46.130.100 offset -0.008529 sec
If you got no answer or errors (no server suitable for synchronization found), check server's configuration - allowed hosts, networks, etc (only if it is the case :-)).
To really adjust the date, as root type ntpdate -b
or ntpdate -b -u Note: this command only perform one request to the server - it should be called from a startup script at boot time. After you got a correct date/time, the regular ntp daemon should take place and keep the time drift under control. Then you should check ntp.drift, etc, etc, etc
http://www.whirlnet.co.uk/linux/ptktime is the utility I use to check my local time is keeping in step with the server. Just make it executable and place it in /usr/local/bin/. I've been using it for years now, amazingly it still works on SuSE 9.1 both x86 and x86_64. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer =====LINUX ONLY USED HERE=====