Bug 119384
| Summary: | /etc/defaults/rc.conf sets wrong path to named.pid | ||
|---|---|---|---|
| Product: | Base System | Reporter: | hsu <hsu> |
| Component: | conf | Assignee: | Doug Barton <dougb> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | 6.3-PRERELEASE | ||
| Hardware: | Any | ||
| OS: | Any | ||
Responsible Changed From-To: freebsd-bugs->freebsd-rc Over to maintainer(s). http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/defaults/rc.conf#rev1.165 http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/defaults/rc.conf#rev1.216 http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/defaults/rc.conf#rev1.217 The first link should have been http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/defaults/rc.conf#rev1.166 State Changed
From-To: open->closed
As the other user ("barbara") was kind enough to point out,
this is by design so that an unprivileged named process can
write to the /var/run/named directory.
Please see the comments in /etc/defaults/rc.conf, about
setting this to the same value in rc.conf and named.conf.
Responsible Changed From-To: freebsd-rc->dougb My area. |
/etc/defaults/rc.conf sets wrong path to named.pid, it says /var/run/named/pid, while the correct path seems to be /var/run/named.pid Fix: Fix: named/pid -> named.pid in /etc/defaults/rc.conf Workaround: set named_pidfile in /etc/rc.conf. How-To-Repeat: sh /etc/rc.d/named restart will complain that named is not running, while it is.