chroot
Kevin Darcy
kcd at daimlerchrysler.com
Wed Apr 25 00:38:47 UTC 2001
Do you understand how chroot() works? Simply put, it makes all of your
pathnames relative to the chroot()'ed directory. So if named would normally
expect to find its configuration file at /etc/named.conf, if it is chroot()'ed
to /var/named it would expect to find the file at /var/named/etc/named.conf.
Any other pathname it uses will also need to be relative to the chroot()
directory.
- Kevin
Norman Zhang wrote:
> Hi,
>
> I am having some problem starting "named" when I added the -t option. If I
> don't use the -t option it works fine. I heard that chroot gives extra
> security.
>
> e.g., daemon named -u named -t /var/named
>
> The error log says that it cannot found /etc/named.conf. I copied
> named.conf, named.boot, rndc.conf to /var/named, but the problem persists. I
> have also copied /var/run/named.pid to /var/named/named.pid. Would someone
> please give me a few pointers? TIA.
>
> Norman
More information about the bind-users
mailing list