On Sun, Nov 06, 2022 at 05:12:12AM +0000, indivC wrote:
> I'm a little confused with the man page for ntpd.
>
> For the '-n' flag, it says:
> 'Configtest mode. Only check the configuration file for validity.'.
> I have no problem with this and understand it.
>
> However, the section below that, which is still under '-n', says:
> 'ntpd will stay in the foreground for up to 15 seconds
> waiting for one of the configured NTP servers to reply.'.
>
> The second section seems to contradict the first, in my opinion.
> If '-n' is only checking the configuration for validity,
> then contacting an NTP server would be outside the scope
> of file validation.
>
> Any clarity on this would be helpful. Thanks.
>
This is a documentation error. The 2nd paragraph should be outside the
option list.
This is bettet I think.
-Otto
Index: ntpd.8
===================================================================
RCS file: /home/cvs/src/usr.sbin/ntpd/ntpd.8,v
retrieving revision 1.45
diff -u -p -r1.45 ntpd.8
--- ntpd.8 11 Nov 2019 17:42:28 -0000 1.45
+++ ntpd.8 6 Nov 2022 06:43:20 -0000
@@ -59,10 +59,6 @@ instead of the default
.It Fl n
Configtest mode.
Only check the configuration file for validity.
-.Pp
-.Nm
-will stay in the foreground for up to 15 seconds waiting for one of the
-configured NTP servers to reply.
.It Fl v
This option allows
.Nm
@@ -87,9 +83,11 @@ option, all calls to
.Xr adjtime 2
will be logged.
.Pp
+At boot,
.Nm
-makes efforts to verify and correct the time at boot if constraints are
-configured and satisfied or if trusted servers or sensors return results,
+wlll stay for a maximum of 15 seconds in the foregorund and make efforts to
+verify and correct the time if constraints are configured and
+satisfied or if trusted servers or sensors return results,
and if the clock is not being moved backwards.
.Pp
After the local clock is synchronized,
