Date: Sat, 30 Apr 2016 09:34:50 -0700 (PDT) From: Roger Marquis <marquis@roble.com> To: "Julian H. Stacey" <jhs@berklix.com> Cc: freebsd-security@freebsd.org, "Matthew X. Economou" <xenophon@irtnog.org> Subject: Re: FreeBSD Security Advisory FreeBSD-SA-16:16.ntp In-Reply-To: <201604301129.u3UBTjWL055247@fire.js.berklix.net> References: <201604301129.u3UBTjWL055247@fire.js.berklix.net>
| previous in thread | raw e-mail | index | archive | help
Large builds over NFS filesystems, particularly secure NFS (i.e., Kerberos) are one the best tests of time synchronization. Clients with bad clocks can further exercise this not uncommon infrastructure. The reason you don't typically see build errors even here, IME, is because the timehosts tend to be shared by and local to both client and server. Roger Julian Stacey wrote: > AMD + NFS makes on a LAN. 1/10 second seems insufficient. > ( Though one could run a faster less secure NTP on a local LAN > behind a firewall, & a slower more secure NTP on a WAN, > (so a FreeBSD gate would need both NTPs ) ).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?>