From owner-freebsd-security Fri Aug 20 15:10:50 1999 Delivered-To: freebsd-security@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id E6D1815395 for ; Fri, 20 Aug 1999 15:10:44 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id AAA06641; Sat, 21 Aug 1999 00:06:41 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) 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> Date: Sat, 21 Aug 1999 00:06:41 +0200 Message-ID: <6639.935186801@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <19990820214657.1605.qmail@alice.gba.oz.au>, Greg Black writes: >> Xntpd is not that difficult. Unlike ntpdate, it can update your system clock >> while also acting as a time server for your local network, reducing bandwidth >> 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. Not any longer with ntpv4... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message