> 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.
KoD packets: us -s 0 -R "RSON" to send those (where RSON is a
4-character string indicating the reason, see
failures: it can print verbosely the contents of the packet for problem
determination
dns caching: it is a ntp server, so doesn't do any dns lookups
I definately like the idea of it being/becoming a test-tool. If you have
any suggestions for that, please do mail them to me.
Folkert van Heusden
--
www.vanheusden.com/multitail - multitail is tail on steroids. multiple
windows, filtering, coloring, anything you can think of
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
