[Bug 197152] rc(8) config files under /usr/local/etc/rc.d/rc.conf.d/ are not sourced at startup

[bugzilla-noreply at freebsd.org]

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

            Bug ID: 197152
           Summary: rc(8) config files under
                    /usr/local/etc/rc.d/rc.conf.d/ are not sourced at
                    startup
           Product: Base System
           Version: 10.1-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: conf
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: jason.mann at gmail.com

OVERVIEW:

The rc.conf(5) man page states the following:

"In addition to /etc/rc.conf.local you can also place smaller configuration
files for each rc(8) script in the /etc/rc.conf.d directory or <dir>/rc.conf.d
directories specified in local_startup, which will be included by the
load_rc_config function."

I have successfully split the contents of my /etc/rc.conf file into multiple
files under /etc/rc.conf.d/ and these are all sourced and correctly acted upon
at system startup.

However, if I relocate the port/package specific files to
/usr/local/etc/rc.d/rc.conf.d/, but they are not acted upon at startup.

The default value of local_startup is "/usr/local/etc/rc.d", as defined in
/etc/defaults/rc.conf.

This departs from the expected behaviour as described in rc.conf(5).


STEPS TO REPRODUCE:

- Relocate a working rc config file from /etc/rc.conf.d/ to
/usr/local/etc/rc.d/rc.conf.d/
- Reboot the system.
- Verify whether the service in question starts on boot.


ACTUAL RESULTS:

- Service is not started at system startup.


EXPECTED RESULTS:

- Service should be started at system startup.


ADDITIONAL INFORMATION:

I tested this on my system with the openntpd and dnsmasq packages.  Both
started fine when their rc config files were under /etc/rc.conf.d/.  Neither
started when those files were moved to /usr/local/etc/rc.d/rc.conf.d/.

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