misc/58134: ntpdate documented as obsolete, and shouldn't be.

Chris chris-gnats33 at randomcamel.net
Thu Oct 16 10:00:41 PDT 2003

>Number:         58134
>Category:       misc
>Synopsis:       ntpdate documented as obsolete, and shouldn't be.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 16 10:00:34 PDT 2003
>Originator:     Chris
>Release:        FreeBSD 4.9-PRERELEASE i386
System: FreeBSD leviathan.houseness.org 4.9-PRERELEASE FreeBSD 4.9-PRERELEASE #20: Sun Sep 28 10:30:19 PDT 2003 root at leviathan.houseness.org:/usr/obj/usr/src/sys/LEVIATHAN i386

        ntpdate, ntpd on -STABLE, going back several years.


        the ntpdate(8) manpage claims:

             Note: The functionality of this program is now
             available in the ntpd(8) program.  See the -q command line
             option in the ntpd(8) page.  After a suitable period of
             mourning, the ntpdate utility is to be retired from this

        and the ntpd(8) manpage claims:

        -q  Exit the ntpd just after the first time the clock is set.
            This behavior mimics that of the ntpdate(8) program, which is
            to be retired.  The -g and -x options can be used with this

        however, ntpd -q has never seemed to work properly, just hanging
        even with an ntp.conf with valid servers. on top of that, ntpdate
        seems to be standard everywhere else (NetBSD and Linux sysadmins
        have never heard of -q), so removing it would violate POLA for
        anyone moving scripts to FreeBSD from other OSen.
        read manpages, try running ntpd -q.

        I'd suggest fixing the manpages and forgetting anyone ever planned
        to obsolete ntpdate, whether this involves emailing the ntp
        maintainers or not. the current manpages are confusing and
        apparently inaccurate.


More information about the freebsd-bugs mailing list