In freebsd-questions Digest, Vol 207, Issue 18, Message: 6
On Fri, 21 Mar 2008 08:54:36 -0500
Martin McCormick [EMAIL PROTECTED] wrote:
I think I fixed it but I am not sure I would have
figured it out quickly without the help from the list.
It seems that FreeBSD defaults to
I think I fixed it but I am not sure I would have
figured it out quickly without the help from the list.
It seems that FreeBSD defaults to a chroot of bind with
the tree owned by root. You can run bind in a sandbox as the
documentation says and have it chroot but if you do, and
At 08:54 AM 3/21/2008, Martin McCormick wrote:
I think I fixed it but I am not sure I would have
figured it out quickly without the help from the list.
It seems that FreeBSD defaults to a chroot of bind with
the tree owned by root. You can run bind in a sandbox as the
About half of the 7 FreeBSD systems I run exhibit a very
annoying behavior that I have not pinned down yet as to why and
how to correct it.
I reboot. Soon, I find that bind isn't running. It runs
as a low-priority process and is owned by bind so it needs to
have write permission
At 06:30 PM 3/20/2008, Martin McCormick wrote:
About half of the 7 FreeBSD systems I run exhibit a very
annoying behavior that I have not pinned down yet as to why and
how to correct it.
I reboot. Soon, I find that bind isn't running. It runs
as a low-priority process and is
On Mar 20, 2008, at 4:30 PM, Martin McCormick wrote:
I reboot. Soon, I find that bind isn't running. It runs
as a low-priority process and is owned by bind so it needs to
have write permission in /var/named. When I do ls -ld on
/var/named, it's owned by root.
/var/named is owned by
Chuck Swiger writes:
/var/named is owned by root on all of my newer (5.x and later)
systems; I found an old 4.11 box with it owned by bind, though. If
you're using named chroot'ed (as recommended), it will want /var/named/
var/{dump/log/run/stats} writable by bind.
That's pretty
