Why doesn't unbound rc.d script require syslogd?

[Igor2022]

FreeBSD 14.0. Neither /usr/local/etc/rc.d/unbound, nor /etc/rc.d/local_unbound list syslogd among their requirements. So, if unbound service (either one) is started by setting respective X_enable="YES" in /etc/rc.conf, then it just so happens that unbound is started before syslogd. Which means that if unbound is configured to use syslog, it won't be able to connect to syslogd, and hence, no messages from unbound will ever make it to syslog files. All unbound messages are simply lost.

Such lack of startup order dependency is quite surprising, especially considering that named (bind918 package) does have such dependency: /usr/local/etc/rc.d/named requires syslogd.

So the question is: why doesn't unbound has such dependency? Is there a reason, or is it just a bug?

P.S. There are other inconsistencies between unbound and named. For one, unbound is scheduled before NETWORKING, while named is scheduled after NETWORKING.

P.S2. Sorry if this is the wrong forum. I was on the fence between "Ports and Packages" and "Web and Network Services"...

 

[Kai Burghardt]

See also PR 262995. Note the common misconception of the REQUIRE statement described in the § Bugs of rcorder(8):​

The REQUIRE keyword is misleading: It does not describe which daemons have to be running before a script will be started. It describes which scripts must be placed before it in the dependency ordering. For example, if your script has a REQUIRE on sshd, it means the script must be placed after the sshd script in the dependency ordering, not necessarily that it requires sshd to be started or enabled.​