Date: Fri, 20 Aug 1999 22:19:48 -0500 From: Jon Hamilton <hamilton@pobox.com> To: Greg Black <gjb-freebsd@gba.oz.au> Cc: Will Andrews <andrews@TECHNOLOGIST.COM>, Brett Glass <brett@lariat.org>, freebsd-security@FreeBSD.ORG Subject: Re: Securelevel 3 ant setting time Message-ID: <19990821031948.09B2B1D@woodstock.monkey.net> In-Reply-To: Your message of "Sat, 21 Aug 1999 07:46:57 %2B1000." <19990820214657.1605.qmail@alice.gba.oz.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <19990820214657.1605.qmail@alice.gba.oz.au>, Greg Black wrote: } > Xntpd is not that difficult. Unlike ntpdate, it can update your system cloc } k } > while also acting as a time server for your local network, reducing bandwid } th } > costs (yes, minimal, if you have a very small network, but still worth time } and } > money.) It is also more reliable and far more featureful than ntpdate (hey, } > encryption compensation!). } } Just as a bit of extra information, xntpd is useless for small } networks that don't have constant connectivity to time servers. Absolutely untrue. There's value in keeping a group of machines synchronized to _each other_, regardless of whether they're also synchronized to the correct time. It is true that _for some purposes_ xntpd isn't all that useful in an intermittently-connected scenario, but that doesn't render it completely devoid of any value. -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990821031948.09B2B1D>