Ceri Davies wrote:
[ ... ]
Please read the section on this in the handbook.
This one:
"17.9.8 Running named in a Sandbox
Contributed by Ceri Davies."
...? :-) Thank you.
-Chuck
Hmm. Quick testing suggests that having a /usr/obj tree lying around
does trigger the problem of staticly linki
On Tue, Jan 28, 2003 at 01:45:27AM -0500, Chuck Swiger wrote:
> I believe the normal way to chroot named in FreeBSD is something like:
>
> named_enable="YES"
> named_flags="-u bind -g bind -t /etc/namedb -c named.conf"
>
> ...in /etc/rc.conf. When doing so, the following seems to make life
> mu
I believe the normal way to chroot named in FreeBSD is something like:
named_enable="YES"
named_flags="-u bind -g bind -t /etc/namedb -c named.conf"
...in /etc/rc.conf. When doing so, the following seems to make life
much better for ndc and the config file:
mkdir /etc/namedb/etc
mkdir /etc/nam
