correct • elegant • free

△ comp.protocols.time.ntp △

◅ Writing and reading time_t values

rdate for FreeBSD

In article <>,
Phil Crown  <> wrote:
>Any tips are welcome.

Well, xntpd may not be simple, but I wouldn't use anything else.  It's
fairly easy to use: it's got excellent autoconfiguration, and lots of
documentation (part of the reason why the distribution is so large).

The key difference between xntpd and other time synchronization methods,
is that xntpd doesn't just discover what time it is, it also discovers
how fast or slow your computer's clock runs, and makes continuous micro
adjustments to compensate.  Once it's settled down, it can keep your
clock accurate to within a few milliseconds sending only one packet
every 20 minutes.

You can use it to keep an isolated network in very close time
synchronization.  Better, if you have an Internet connection, you can
get real UTC, with leap seconds and all, from public NTP servers (such
as ntp[012]

If you've got FreeBSD, you've already got xntpd.  To start it up, just


in /etc/sysconfig, and put something like this in /etc/ntp.conf.

    # External peers

    # Local peers

    driftfile /etc/ntp.drift

Tim Goodwin | "I suppose this is another case of those darn IP/TCP guys who
UUNET, UK   | work in practice but not in theory." -- Paul Mockapetris

Original headers:

From: (Tim Goodwin)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: rdate for FreeBSD
Date: 30 Apr 1997 09:59:29 GMT
Organization: UUNET, Cambridge, UK.
Message-ID: <5k7561$>

△ comp.protocols.time.ntp △

◅ Writing and reading time_t values