Stephen Vaughan wrote: > Okay, but surely the version isn't causing this problem?
It may be, if you are using your more than four year old version 4.2.2p1 circa Jul of 2006, and the issue was fixed by 4.2.4p8 circa 2009. > version="ntpd [email protected] Thu May 14 13:01:41 UTC 2009 (1)", I think there have been some more recent changes to 4.2.7 (& 4.2.6 ?) {related to pool server use?} that might improve recovery of transient unreachability. Although I'd guess 4.2.4 stable or later might resolve your issue, why not try the latest stable, or even a more recent 4.2.7 dev that fixes many other issues. <http://archive.ntp.org/ntp4/ntp-4.2/ntp-4.2.6p2.tar.gz> <http://support.ntp.org/bin/view/Main/SoftwareDownloads> <http://ntp.org/downloads.html> Certainly worth a try. IIRC there a a few people here who run NTP on laptops, as well as others on dynamic IP networks, that don't always have connectivity that have found workarounds for older versions of NTP. Some flavor of monitoring app, that queries NTP and check the status of peer associations, restarting NTP if necessary. e.g. parsing the output from "ntpq -c as" or perhaps "ntpq -p" Ref: Bug 622 (dynamic-if) Target Milestone: 4.2.4 <Block Quote> Functionality: - automatically bind to newly configured network interfaces - allow associations to be configured even when the current network configuration would not support that - keep (configured) associations even when the interface goes away - remove hard coded limit on number of interfaces (now only limited by libisc limits) - check for interface changes via routing socket on systems that support it. - add ntpdc commands ifstats (display current interface list), ifreload (re-check interfaces) ... to be integrated in ntp-dev after release of 4.2.2 See also: Bugs 51, 244, 310, 314, 330, 549 -- E-Mail Sent to this address <[email protected]> will be added to the BlackLists. _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
