On Thu, Dec 22, 2016 at 04:17:03PM -0700, Roger Koehler wrote: > > > > On the http://www.pool.ntp.org/en/use.html website, it states: > > > > "Make sure your computer's clock is set to something sensible (within > > a few minutes of the 'true' time) - you could use ntpdate > > pool.ntp.org." I'll try adding that to init.d/ntpd. > > It worked! I just put this line above the line that starts the daemon. > It takes about 6 seconds instead of several minutes. Note: From this > same website it says, "[synchronization can] take as long as half an > hour!". When your clock comes up at Dec. 31, 1969, this is not an > option! > > To the editors: I would recommend that you add this line (ntpdate > <***EDITME***pool.ntp.org***EDITME***>) above the line that starts the > daemon in init.d/ntpd. You could probably leave off the ***EDITME*** > since this should work from any location that has external internet > access.
Late reply (I've been offline for a bit over a week - hardware failures in both what is effectively the router and also in one of my switches) - so what happens if there is no internet for some reason ? Does ntpdate time out in a short time (like dhclient and nfs mounts) ? And can I suggest that you invest in a new battery for that motherboard ? ĸen -- `I shall take my mountains', said Lu-Tze. `The climate will be good for them.' -- Small Gods -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
