[ntp:questions] Re: ntpd, boot time, and hot plugging

David L. Mills mills at udel.edu
Fri Feb 4 02:24:15 UTC 2005


I have no idea what you are assuming about start/stop. The scheme I 
mentioned has nothing to do with that, just the number of responses 
necessary to set the clock. The only practical way to disciplne the time 
when hibernating or changing wifi cards is using the TOY chip and this 
can be quite accurate if the scheme I mentioned in my last is adopted.

PLEASE NOTE: There have been a number of changes since the 4.2.0 
distribution, which is now well over a year old. Some of the schemes I 
have mentioned here are only in recent versions.


Kenneth Porter wrote:

> "David L. Mills" <mills at udel.edu> wrote in news:cttv9l$ql7$1
> @dewey.udel.edu:
>>It is true that ntpd is specifically engineered for Internet badlands 
>>where popcorn spikes, evil masqueraders, misbehaving clocks and other 
>>vermin might poison your DNS cache. A client using the pool servers 
>>scheme really needs this ammunition.
> What about mobile clients? In the mobile environment, what does ntpd do 
> when you sever the network connection (ie. undock)? Suppose I undock 
> (taking down eth1) and plug in down the hall with the built-in NIC 
> (bringing up eth0). What must one do to make ntpd tolerant of that? Or must 
> mobile apps give up quality time because their network interfaces are 
> transient? Would one need to script a complete stop/start of ntpd whenever 
> interfaces come and go?

More information about the questions mailing list