This is one reason why ntp setups typically use 0.pool... 1.pool... 2.pool... etc. There is available data from multiple sources, and survivability of one of the sources is down (or responding badly).
A sane ntp client will be nearly (completely?) unaffected by one of the timeservers not responding on any given request cycle. That said, it wasn't you that lost availability last night. It was the monitoring server. -drew On 2007/08/17, at 4:11, Tim Shoppa wrote: > I notice that it has "dinged" my ntp server (in Eastern US) > a couple times in the past day without any obviously large time > offset, which > I assume to mean that my network wasn't talking to the monitoring > site's network a couple times in the past day. Not the smoothest > operation but not too bad and any sane ntp client would either > ride these network glitches out or just switch to a reachable server, > right? > > Tim. > >>>> M Graff <[EMAIL PROTECTED]> 8/17/2007 4:15 AM >>> > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I cannot reach it from my Cox cable connection at least... It almost > looks like the IP space it lives in has become unrouted. > > - --Michael > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (MingW32) > > iD8DBQFGxVkpuzMQWQwZDN0RAtWWAKCUx15x3KVmAn/R1Bh6Fp/gJRaS3ACfWcbP > 81Gq4SZWZTz0zwrLk8AOwes= > =TOxf > -----END PGP SIGNATURE----- > _______________________________________________ > timekeepers mailing list > [email protected] > https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers > > _______________________________________________ > timekeepers mailing list > [email protected] > https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers -- M. Drew Streib [EMAIL PROTECTED] _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
