On Friday 16 December 2005 18:26, Paul W. Abrahams wrote: <snip>
I just discovered ... that ntpd was not being started at boot time
When I configure it in YaST, all I do is enter my preferred time server and test the connection (after dropping the firewall). When I click 'Finish' or 'OK' or whatever that label is, the process is done and ntpd starts at boot. Did you configure it manually, by editing files, or did you set it up in YaST?
I don't understand why the default is to not run ntpd. In any event, I've turned it on now, so I'll see if my clock keeps better time.
Per the above, it would/should have been starting at boot if you configured it in YaST
But that still leaves the following question. If ntpd relies only on the drift file to keep the system clock accurate, sooner or later the system clock will wander. Supposedly if ntpd is running, the drift value is updated on halt. But what if the machine is never turned off? Is there some way to get ntpd to consult its collection of timeservers periodically and/or update the drift value?
This hypothetical style of questioning is hard to respond to without rolling up one's sleeves, digging into the documentation and doing a lot of research -- unless you're a Linux guru, of course. I prefer to just give the creators of the ntp system credit for understanding how to keep time accurate on a system that runs 24x7. I could be wrong... I've been wrong before... but mine just works here. Your's should, too. regards, - Carl