On 29 Apr 2013 at 21:14, Jason Cipriani wrote: > I am currently working on a project where 60 devices, all behind a router > with one WAN IP, update their time from north-america.pool.ntp.org on boot. > They > all boot at the same time. > > I frequently run into rate limit errors. > > I am going to add a small random delay to the initial NTP update to spread > out the requests a bit. What is the actual rate limit? > > Thanks, > Jason >
<http://www.pool.ntp.org/en/use.html> has: ! If you are synchronising a network to pool.ntp.org, ! please set up one of your computers as a time server ! and synchronize the other computers to that one. ! (you'll have some reading to do - it's not difficult ! though. And there's always the comp.protocols.time.ntp ! newsgroup.) I've setup my four local internet servers to run ntpd with two of them in the pool. PCs on my lan sync to my own local internet and file servers not to any external servers and sometimes at startup will be rate limited by my own servers. My laptops use burst option with a large minpoll, otherwise when used via a mobile wireless connection, delay can result in offset >> 1 sec, whilst burst and an established drift file gives an offset < 10 ms. David -- David Lord <[email protected]> <ftp://ftp.lordynet.org/pub/pgpkeys/[email protected]/> <http://www.lordynet.org/pub/pgpkeys/[email protected]/> <file=pubkey.asc> _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
