1 |
I did a update --world tonight and I also ran into this. It's probably |
2 |
destined for bugzilla, but I wanted to ask first. |
3 |
|
4 |
After updating to bind-9.1.3-r7 I had a problem getting it to run. I |
5 |
determined the problem to be the following. The named startup script |
6 |
executes this: start-stop-daemon --start --quiet --exec /usr/sbin/named -- -u named -n 1 |
7 |
|
8 |
Since named switches to uid 'named' it doesn't have access to write to |
9 |
/var/run/named.pid However, I noticed that there is now a |
10 |
/var/run/named dir that is owned by named.named...This is all well and |
11 |
good but the named binary doesn't try to write it's pidfile to that |
12 |
directory and bombs. I looked in the ebuild and the bind documentation |
13 |
and there is a way to configure it to point to another directory: on the |
14 |
configure script it needs --localstatedir=/var/run/named instead of |
15 |
--localstatedir=/var but this also means that the /etc/init.d/named |
16 |
script needs to be edited to point to /var/run/named/run/named.pid for |
17 |
the stop portion of it. Maybe the extra 'run' in there could be edited |
18 |
out with by modifing the bind source, I didn't dig that far, I just need |
19 |
it running. :) |
20 |
Also /var/bind needs to be owned by named.named in order for the zone |
21 |
files to be read (since I did an upgrade, this bit me, it may not on a |
22 |
new install) |
23 |
-- |
24 |
Todd Punderson <todd@××××××.net> |