Date: Fri, 09 Mar 2018 18:16:09 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 226484] dns/unbound unable to stop through rc.d script when specifying alternate PID file location Message-ID: <bug-226484-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226484 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@FreeBSD.org Reporter: driesm.michiels@gmail.com CC: jaap@NLnetLabs.nl CC: jaap@NLnetLabs.nl Flags: maintainer-feedback?(jaap@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. Altoug= h it reflects the daemon can't handle an alternate PID file location. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-226484-13>