1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
|
$FreeBSD$
--- ntpd.conf.5.orig 2009-11-23 21:03:30.000000000 +0100
+++ ntpd.conf.5 2009-11-23 21:12:27.000000000 +0100
@@ -59,62 +59,6 @@ or
listen on 127.0.0.1
listen on ::1
.Ed
-.It Xo Ic sensor Ar device
-.Op Ic correction Ar microseconds
-.Op Ic weight Ar weight-value
-.Op Ic refid Ar string
-.Xc
-Specify a timedelta sensor device
-.Xr ntpd 8
-should use.
-The sensor can be specified multiple times:
-.Xr ntpd 8
-will use each given sensor that actually exists.
-Non-existent sensors are ignored.
-If
-.Sq *
-is given as device name,
-.Xr ntpd 8
-will use all timedelta sensors it finds.
-.Xr ntpd 8
-does not use any timedelta sensor by default.
-For example:
-.Bd -literal -offset indent
-sensor *
-sensor nmea0
-.Ed
-.Pp
-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 70ms behind
-actual time:
-.Bd -literal -offset indent
-sensor udcf0 correction 70000
-.Ed
-.Pp
-The optional
-.Ic weight
-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.
-.Pp
-An optional reference ID string - up to 4 ASCII characters - can be
-given to publish the sensor type to clients.
-RFC 2030 suggests some common reference identifiers, but new identifiers
-"can be contrived as appropriate."
-If an ID string is not given,
-.Xr ntpd 8
-will use a generic reference ID.
-For example:
-.Bd -literal -offset indent
-sensor nmea0 refid GPS
-.Ed
.It Xo Ic server Ar address
.Op Ic weight Ar weight-value
.Xc
@@ -139,6 +83,17 @@ server ntp.example.org weight 1
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.
+.Pp
+The optional
+.Ic weight
+keyword permits finer control over the relative importance
+of time sources.
+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.
.It Xo Ic servers Ar address
.Op Ic weight Ar weight-value
.Xc
@@ -157,15 +112,14 @@ servers pool.ntp.org
.Ed
.El
.Sh FILES
-.Bl -tag -width "/etc/ntpd.confXXX" -compact
-.It Pa /etc/ntpd.conf
+.Bl -tag -width "%%PREFIX%%/etc/ntpd.confXXX" -compact
+.It Pa %%PREFIX%%/etc/ntpd.conf
default
.Xr ntpd 8
configuration file
.El
.Sh SEE ALSO
-.Xr ntpd 8 ,
-.Xr sysctl 8
+.Xr ntpd 8
.Sh HISTORY
The
.Nm
|
