Roger Oberholtzer wrote:
On Mon, 2011-07-18 at 15:01 +0200, Per Jessen wrote:
Anton Aylward wrote:
Your reasoning is valid, but it is also an example of a much more general problem, that of dependencies.
You are stating, quite rightly, that NTP should be started when a specific network comes up.
Provided that ntp is properly configured, it doesn't really matter.
My ntp setup is out-of-the-box openSUSE. All I have done is select a time server via YaST. I have been saving the fun of learning the details of ntp configuration for when I start using GPS/PPS in a road vehicle.
Have you made changes to ntp to achieve your fantasmagorical ntp robustness?
Hehe, nothing fantastic about it, it is really standard - here is my main server config, comments omitted: server 127.127.8.1 mode 16 prefer # dcf77 server 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized server ntp.metas.ch server swisstime.ethz.ch driftfile /var/lib/ntp/drift/ntp.drift # path for drift file logfile /var/log/ntp # alternate log file logconfig =all I don't use NetworkManager, and my systems run all the time. The hardware clock is of course UTC, local time is CET/CEST. -- Per Jessen, Zürich (19.5°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org