kiran shirol wrote: > Frank, > > That would be good so that the user need not have to worry about any changes > in the IP addresses in > future.
This statement seems to be implying that ntpd does not detect interface changes. This is *NOT* the case for 4.2.4 and after. ntpd 4.2.4 *detects* changes in interface addresses and routing. I may take a while for some platforms (Windows/Linux - BSD is almost instant as it is event driven). The default rescans every 5 minutes. This can be lowered to 1 minute with the -U 60 switch. -U 0 disables scanning. The lower limit of 60 seconds will be dropped in the future. The default where choosen for a reasonable balance between computational load and responsiveness. Thus don't expect an instant response when you are on a platform where we have yet to implement the event mechanism. Just wait a bit. It is documented in the html pages an in the short help of the daemon. I read some other mail thread on the forum and the solution > suggested was to restart NTP. But > that approach needs user/admin intervention and thus not a good thing to do. > I will keep a watch on the > bug IDs too. > > Thanks Frank for the responses. > > Kiran > [snip] Frank _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
