Nelis Lamprecht wrote:
> Oops my bad. The only other explanation I can think of then is that
> the path for the pid file may be specified incorrectly in your
> named.conf in relation to your chroot ?
I thought that too. First, I had no path specified in named.conf,
defaults to /var/run/named.pid - relative to the (ch)root dir.
I tried to specify that path with and without leading / in named.conf,
options { pid-file }. Same result.
Starting up with '-u root' creates a pid-file where I expect, and the
directory has correct permissions as listed in previous post.
I have now tried this:
# chroot -u bind -g bind /var/named /usr/local/sbin/named -c \
/etc/named.conf
This starts up bind and a pid file is correctly created in
${CHROOTDIR}/var/run but since prileges are dropped before binding to
the interface it runs on an unprivileged port. Not really satisfying
either :-(
And this fails:
# chroot /var/named /usr/local/sbin/named -g -u bind -t / -c \
/etc/named.conf
with the same error as before. Somehow it appears that named tries to
create a pid file as a user that is not 'bind' nor 'root'. Is there some
way I can get that information out?
Mystery deepens...?
Thanks, Erik
--
Ph: +34.666334818 web: www.locolomo.org
S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt
Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9
Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2
_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
