diff options
| author | Karel Zak | 2018-07-31 11:07:47 +0200 |
|---|---|---|
| committer | Karel Zak | 2018-07-31 11:07:47 +0200 |
| commit | 6df5c6d4e0461ac0b7a4f274ae6ee16b72e951f9 (patch) | |
| tree | a0126a0165414ef8152d0dbeaff6fbf10c5eb1ac /sys-utils/hwclock.8.in | |
| parent | lscpu: fix resource leak [coverity scan] (diff) | |
| download | kernel-qcow2-util-linux-6df5c6d4e0461ac0b7a4f274ae6ee16b72e951f9.tar.gz kernel-qcow2-util-linux-6df5c6d4e0461ac0b7a4f274ae6ee16b72e951f9.tar.xz kernel-qcow2-util-linux-6df5c6d4e0461ac0b7a4f274ae6ee16b72e951f9.zip | |
hwclock: remove ntpd from man page
It seems better to use generic "NTP daemon" in the man page than
points to specific ntpd(1) implementation as some distros use for
example chronyd(1) rather than old ntpd(1).
Signed-off-by: Karel Zak <kzak@redhat.com>
Diffstat (limited to 'sys-utils/hwclock.8.in')
| -rw-r--r-- | sys-utils/hwclock.8.in | 11 |
1 files changed, 4 insertions, 7 deletions
diff --git a/sys-utils/hwclock.8.in b/sys-utils/hwclock.8.in index 729b1ddae..bef7a3170 100644 --- a/sys-utils/hwclock.8.in +++ b/sys-utils/hwclock.8.in @@ -412,7 +412,7 @@ at shutdown; with the old behaviour this would automatically (re)calculate the drift factor which caused several problems: .RS .IP \(bu 2 -When using ntpd with an \%'11\ minute\ mode' kernel the drift factor +When using NTP with an \%'11\ minute\ mode' kernel the drift factor would be clobbered to near zero. .IP \(bu 2 It would not allow the use of 'cold' drift correction. With most @@ -689,7 +689,6 @@ variable is unset. This value is output as the 'status' line of the .BR \%adjtimex\ --print " or " \%ntptime " commands." .PP It takes an outside influence, like the NTP daemon -.BR ntpd (1), to put the kernel's clock discipline into a synchronized state, and therefore turn on \%'11\ minute\ mode'. It can be turned off by running anything that sets the System Clock the old @@ -744,8 +743,7 @@ are supported by the hardware. .PP This discussion is based on the following conditions: .IP \(bu 2 -Nothing is running that alters the date-time clocks, such as -.BR \%ntpd "(1) or a cron job." +Nothing is running that alters the date-time clocks, such as NTP daemon or a cron job." .IP \(bu 2 The system timezone is configured for the correct local time. See below, under .BR "POSIX vs 'RIGHT'" . @@ -764,8 +762,7 @@ During shutdown the following is called: .BR * " Systems without " adjtimex " may use " ntptime . .in .PP -Whether maintaining precision time with -.BR \%ntpd (1) +Whether maintaining precision time with NTP daemon or not, it makes sense to configure the system to keep reasonably good date-time on its own. .PP @@ -827,7 +824,7 @@ cold drift should yield better results. .PP .B Steps to calculate cold drift: .IP 1 2 -.RB "Ensure that " ntpd "(1) will not be launched at startup." +.RB "Ensure that NTP daemon will not be launched at startup." .IP 2 2 .RI The " System Clock " "time must be correct at shutdown!" .IP 3 2 |