On Aug 19, 2010, at 13:16:55, Ask Bjørn Hansen wrote: > For leaving the pool this is a terrible idea. Most/all SNTP clients will > pickup the change quickly. Ntpds won't by design -- not really the users > fault. Future ntpd versions will handle this better. > > However: as a test tool this has great potential! Set it up to run on a > couple of IPs with logging and a log analyzer and it could be an (automated?) > test tool for people implementing clients. > > Does it deal appropriately with failures? With KoD packets? DNS caching... > Etc etc. > > -- > http://localrobot.com/ > Once you've left the pool, why not just block it with iptables/ipfilter, etc? That's what I usually do. It may be "rude" but it gets the point across.
Scott _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
