[Bug 226484] dns/unbound unable to stop through rc.d script when specifying alternate PID file location

[bugzilla-noreply at freebsd.org]

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

            Bug ID: 226484
           Summary: dns/unbound unable to stop through rc.d script when
                    specifying alternate PID file location
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: driesm.michiels at gmail.com
                CC: jaap at NLnetLabs.nl
                CC: jaap at NLnetLabs.nl
             Flags: maintainer-feedback?(jaap at NLnetLabs.nl)

When speficying an alternate location of the PID file. The rc.d script is
unable to determine PID file location after that the daemon has started.

I have the following settings in unbound.conf:
        chroot: ""
        directory: "/usr/local/etc/unbound"
        pidfile: "/var/run/unbound.pid"

When starting unbound, the program creates the PID file at the location
specified. All good here.

When issuing "service unbound stop" the following output is reflected:
unbound not running? (check /usr/local/etc/unbound/unbound.pid).

While it is running. It seems like the PID file is hardcoded in the source.
Or not? Because I'd think it isn't as its a setting in unbound.conf. Altough it
reflects the daemon can't handle an alternate PID file location.

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