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/ On Aug 19, 2010, at 6:30, folkert <[email protected]> wrote: > Hi, > > For people who left the NTP pool, it might be usefull to run > http://www.vanheusden.com/time/jans/ for a while: it acts as a real NTP > server but then returing random or constant or backticking time. People > might then realise sooner that something is wrong (=they're using a no > longer existing server). > > > Folkert van Heusden > > -- > Feeling generous? -> http://www.vanheusden.com/wishlist.php > ---------------------------------------------------------------------- > Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com > _______________________________________________ > pool mailing list > [email protected] > http://lists.ntp.org/listinfo/pool _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
