.TH NTPD.CONF 5 "$Mdocdate: October 2 2007 $" ""
.SH NAME
\fBntpd.conf\fP
\- Network Time Protocol daemon configuration file
.SH DESCRIPTION
This manual page describes the format of the
\fBntpd\fP(8)
configuration file.

The optional
\fBweight\fP
keyword permits finer control over the relative importance
of time sources (servers or sensor devices).
Weights are specified in the range 1 to 10;
if no weight is given,
the default is 1.
A server with a weight of 5, for example,
will have five times more influence on time offset calculation
than a server with a weight of 1.

\fBntpd.conf\fP
has the following format:

Empty lines and lines beginning with the
`#'
character are ignored.

Keywords may be specified multiple times within the configuration file.
They are as follows:
.TP
\fBlisten on \fIaddress\fP\fP
OpenNTPd has the ability to sync the local clock to remote NTP servers and, if this directive is specified, can act as NTP server itself, redistributing the local clock.

Specify a local IP address or a hostname the
\fBntpd\fP(8)
daemon should listen on to enable remote clients synchronization.
If it appears multiple times,
\fBntpd\fP(8)
will listen on each given address.
If
`*'
is given as an address,
\fBntpd\fP(8)
will listen on all local addresses.
\fBntpd\fP(8)
does not listen on any address by default.
For example:

listen on *
.br

or

listen on 127.0.0.1
.br
listen on ::1
.br
.TP
\fBsensor \fIdevice\fP\fP [\fBcorrection \fImicroseconds\fP\fP] [\fBweight \fIweight-value\fP\fP] 
Specify a timedelta sensor device
\fBntpd\fP(8)
should use.
The sensor can be specified multiple times:
\fBntpd\fP(8)
will use each given sensor that actually exists.
Non-existent sensors are ignored.
If
`*'
is given as device name,
\fBntpd\fP(8)
will use all timedelta sensors it finds.
\fBntpd\fP(8)
does not use any timedelta sensor by default.
For example:

sensor *
.br
sensor udcf0
.br

An optional correction in microseconds can be given to compensate
for the sensor's offset.
The maximum correction is 127 seconds.
For example, if a DCF77 receiver is lagging 15ms behind
actual time:

sensor udcf0 correction 15000
.br
.TP
\fBserver \fIaddress\fP\fP [\fBweight \fIweight-value\fP\fP] 
Specify the IP address or the hostname of an NTP
server to synchronize to.
If it appears multiple times,
\fBntpd\fP(8)
will try to synchronize to all of the servers specified.
If a hostname resolves to multiple IPv4 and/or IPv6 addresses,
\fBntpd\fP(8)
uses the first address.
If it does not get a reply,
\fBntpd\fP(8)
retries with the next address and continues to do so until a working address
is found.
For example:

server 10.0.0.2 weight 5
.br
server ntp.example.org weight 1
.br

To provide redundancy, it is good practice to configure multiple servers.
In general, best accuracy is obtained by using servers that have a low
network latency.
.TP
\fBservers \fIaddress\fP\fP [\fBweight \fIweight-value\fP\fP] 
As with
\fBserver\fP,
specify the IP address or hostname of an NTP server to synchronize to.
If it appears multiple times,
\fBntpd\fP(8)
will try to synchronize to all of the servers specified.
Should the hostname resolve to multiple IP addresses,
\fBntpd\fP(8)
will try to synchronize to all of them.
For example:

servers pool.ntp.org
.br
.SH FILES
.TP
.B /etc/openntpd/ntpd.conf
default
\fBntpd\fP(8)
configuration file
.SH SEE ALSO
\fBntpd\fP(8),
\fBsysctl\fP(8)
.SH HISTORY
The
\fBntpd.conf\fP
file format first appeared in
OpenBSD 3.6 .