[Bug 199127] rc.d/ntpd: user-set ntpd_flags stomps over rc-defined ones (pidfile, driftfile)

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199127

            Bug ID: 199127
           Summary: rc.d/ntpd: user-set ntpd_flags stomps over rc-defined
                    ones (pidfile, driftfile)
           Product: Base System
           Version: 9.2-STABLE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: conf
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: jdc at koitsu.org

Issue:

Use of ntpd_flags in /etc/rc.conf results in completely broken behaviour when
ntpd starts.  The most common issue is that there is no longer a pidfile
associated with ntpd, as well as other problems.

This is caused by a design/logic problem in etc/rc.d/ntpd which I have not yet
worked out.  I am certain it must be easy/simple, and hoping someone in the
FreeBSD team can figure it out easier than I can.

Reproducing:

rc.conf contains following settings:

ntpd_enable="yes"
ntpd_config="/conf/ME/ntp.conf"
ntpd_sync_on_start="yes"

Process starts as:

/usr/sbin/ntpd -g -c /conf/ME/ntp.conf -p /var/run/ntpd.pid -f
/var/db/ntpd.drift

Add the following line to rc.conf:

ntpd_flags="-4"

Process starts as:

/usr/sbin/ntpd -g -c /conf/ME/ntp.conf -4

Note missing -p and -f.  This causes lots of problems (like service/rc scripts
saying "ntpd: no such pid", etc.).

This is on a stable/9 system (9.3-STABLE, which is not a choice in the Bugzilla
pulldown for some reason).  No idea if stable/10 has this fixed (haven't
looked, but if it has, it should be MFC'd).

Footnote: this may or may not somehow be related to Bug 106927.

-- 
You are receiving this mail because:
You are the assignee for the bug.