From owner-freebsd-security Fri Aug 20 20:21:32 1999 Delivered-To: freebsd-security@freebsd.org Received: from mailgw02.execpc.com (mailgw02.execpc.com [169.207.3.78]) by hub.freebsd.org (Postfix) with ESMTP id D403215300 for ; Fri, 20 Aug 1999 20:21:29 -0700 (PDT) (envelope-from hamilton@pobox.com) Received: from woodstock.monkey.net (mercury-1-124.mdm.mkt.execpc.com [169.207.87.124]) by mailgw02.execpc.com (8.9.1) id WAA21139; Fri, 20 Aug 1999 22:19:22 -0500 Received: from pobox.com (localhost [127.0.0.1]) by woodstock.monkey.net (Postfix) with ESMTP id 09B2B1D; Fri, 20 Aug 1999 22:19:48 -0500 (CDT) To: Greg Black Cc: Will Andrews , Brett Glass , freebsd-security@FreeBSD.ORG Subject: Re: Securelevel 3 ant setting time In-reply-to: Your message of "Sat, 21 Aug 1999 07:46:57 +1000." <19990820214657.1605.qmail@alice.gba.oz.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Aug 1999 22:19:48 -0500 From: Jon Hamilton Message-Id: <19990821031948.09B2B1D@woodstock.monkey.net> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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