On Friday 16 December 2005 6:50 pm, Carl Hartung wrote:
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
I have indeed configured it in Yast now, and it's running as we speak. But I'm still curious why it was necessary to do that. I would have thought that the best default would be to start ntpd on boot rather than not to start ntpd on boot. So this is a "why" question, not a "how" question.
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.
I'll know in a day or so if it "just works", but I expect at this point that it will. And I have no doubt that the creators of the ntp system got it right. But I'm still curious about certain aspects of how it works. Paul