On 10/4/06, John Andersen
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.
ding ding ding ... I'll bet that is it. This is a laptop, therefore I shut it down frequently and I almost exclusively connect via wireless -- and, most of the places I go, I have to manually select the wireless access point. So essentially what you are saying is that NTP does not startup if there is no network. Fine. Seems like yet another extra step to have to take, but ... fine. I'll make the burst and iburst changes on the server to see if this addresses the issues there. So, the command to execute from a script on my laptot is rcntp restart .. is there anyway to associate that with the wireless network coming up, so that I don't have to do this extra little step each time?
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.
I don't understand why you would not want/expect YAST to work. Seems to me that if the distro provides a management tool, then it should do it's job. Yes, I can learn to manage every system with the conf files ... but, really, while I may want to develop linux skills as an end in itself, most of my customers simply want to use linux to do a job. Hence the management tools, and why they should work.
Oh, and whats this reboot stuff... don't do that. All you need is: rcntp restart
the reboots were only because this is a laptop ....
Just to be pedantic I've pasted my /etc/ntp.conf in below for comparison.
thank you, I appreciate the pedantry and the examples! Peter