On Tuesday 03 October 2006 21:24, Peter Van Lone wrote:
p02-dcs13:~ # xntpdc -p remote local st poll reach delay offset disp ======================================================================= *LOCAL(0) 127.0.0.1 10 64 377 0.00000 0.000000 0.03078
This, despite the fact that I have specified a time server in the config, and that the server tested properly (ie no issue with needing to drop the firewall).
If I then go back into YAST to look at the settings (just checking, you know!) but don't change the server that is listed, then, when I issue the xntpdc -p command (and it is the same if I do xntpdc and then type peers at the ntp prompt), I get:
p02-dcs13:~ # xntpdc -p xntpdc: read: Connection refused
Then, if I go back into YAST and change the time server ... when I issue the xntpdc -p command, I get:
p02-dcs13:~ # xntpdc -p remote local st poll reach delay offset disp ======================================================================= =LOCAL(0) 127.0.0.1 10 64 1 0.00000 0.000000 2.81735 =taylor.cs.wisc. 192.168.2.100 2 64 1 0.04097 -0.002045 1.98431 p02-dcs13:~ #
You should have a look at the log in /var/log/ntp
Chances are there will be some indication in there as to why it rolled over
and died, (if it did indeed die).
Note that ntpd will refuse to try to sync if your machine clock is hopelessly
out of sync with the reference clock, by (I forget the exact limit) some
fairly large number of minutes.
Also (obviously) ntp needs the network to be up before it can sync, so
you have to make sure the init scripts are run in the right order, but unless
you've been messing with them, SuSE usually gets those right. Still
bears checking that in run level 3 and 5 that the xx in Sxxntp is higher than
Sxxnetwork, and that you actually have a working network at the
time ntp starts.
Then take a look at your /etc/ntp.conf with your favorite editor. As Carl
mentioned its a simple file, and more easily managed at the command line
than thru yast.
Oh, and whats this reboot stuff... don't do that.
All you need is:
rcntp restart
Just to be pedantic I've pasted my /etc/ntp.conf in below for comparison.
BTW: The time zone of the reference clock does not matter. For years
before there were local references in alaska I synced with NIST in Colorado
and a clock in Japan. But now that the University of Alaska is on internet 2
their clock is "closer" than any others. So, what I'm getting at here is that
you could SAVE A BACKUP of your /etc/ntp.conf and swap in mine
to see how it works.
---begin paste
################################################################################
## /etc/ntp.conf
##
## Sample NTP configuration file.
## See package 'ntp-doc' for documentation, Mini-HOWTO and FAQ.
## Copyright (c) 1998 S.u.S.E. GmbH Fuerth, Germany.
##
## Author: Michael Andres,