On Jan 28, 2007, at 3:34 PM, Mike Bird wrote:
On Monday 22 January 2007 16:49, Bruno Voigt wrote:
Hi,
I'm running debian/unstable on my laptop and often the LAN/WLAN is
not
connected (yet)
when the system is starting up - including NTPD.
NTPD then seems to discard all unreachable server entries and ends up
with no peers left.
In some googled doc I found the ntp.conf option "dynamic" to tell it
that some peers may become available later on,
but the debian ntpd doesnt't seem to understand it - or I don't
know how
to use it correctly.
What is the best way to configure the ntpd in such an environment ?
Just configure ntpd as normal, but add an hourly cronjob which does
"/etc/init.d/ntp restart >/dev/null".
A client has a server on PPPOE where ntpd always fails at the outset.
Using this, rather than ntpdate, results in the clock staying in sync
without stepping. The hwclock is good enough for ntpd after reboot
(or DSL outage) until the next time the cronjob runs.
--Mike Bird
I like that idea. It avoids ntpdate, which (for better or for worse,
is deprecated by the NTP developers and will not be getting timely
updates in the future) and it gives ntpd a chance to do it's starting
transient thing (fairly recently added) and thus get the parameters
right if it can talk to the Internet servers. And it does no
(serious) harm if you're disconnected from the Internet when the cron
runs.
Worth a try!
Rick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
