On 10/3/06, Carl Hartung
On Tuesday 03 October 2006 00:07, John Andersen wrote:
On Monday 02 October 2006 06:44, Carl Hartung wrote:
My understanding is you really only want to sync to *one* known reliable server (or pool) because the syncing process is just that: a process which takes time to complete.
Not exactly Carl.
Well, sort of...
NTP is smart enough to pick the best server from a bunch.
Yes, if you have such a critical time sensitive application, otherwise you should conserve the traffic. And the point that I was actually focusing on was this: syncing is a process, not a one time event. You don't a) set it up b) expect the time to correct itself immediately and c) when it doesn't, start 'server shopping'. Is that clearer? ;-)
I have followed this thread with interest, because it has not seemed to me, that configuring the ntp client just has not really worked to keep either a SLES or my current suse 10.0 desktop synced. So, following the advice in the cool solutions article to add the burst and iburst paraemeters in advanced settings. However, this is what still seems to be happening: Before going into yast, but after reboot (if I had made changes to the ntp client earlier), when I issue the command xntpdc -p I get: 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:~ # However, after a reboot, I am back to square 1, with only the local server showing. So, what the ??? It seems like this should be pretty damn simple ... Peter