Date: Sun, 14 Jul 2002 11:31:49 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Stacey Roberts <sroberts@dsl.pipex.com> Cc: FreeBSD-Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Cannot start bind in samdbox? Message-ID: <20020714103149.GB25158@happy-idiot-talk.infracaninophi> In-Reply-To: <1026640255.97896.9.camel@Demon.vickiandstacey.com> References: <1026640255.97896.9.camel@Demon.vickiandstacey.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 14, 2002 at 10:50:54AM +0100, Stacey Roberts wrote:
> I'm trying to set named up on a box here, following the handbook as
> well as FBSD Unleashed - but I cannot seem to get bind started and going
> in a sandbox.
>
> This is the error I keep getting:
> # /usr/sbin/named -u bind -g bind -t /etc/namedb/s/
> can't open '/etc/namedb/named.conf'
> #
If your named.conf file is in the usual place, /etc/namedb/named.conf,
then it's going to be inaccessible to named once it's performed the
chroot(2) to /etc/named/s
You need to replicate all of the file structure of /etc/namedb to your
chroot directory. Try this:
mkdir /var/named
cd /
tar -cf - etc/namedb | (cd /var/named ; tar -xvpf - )
Now when you start up named, use the command line:
/usr/sbin/named -u bind -g bind -t /var/named
named should then be happily reading the file
/var/named/etc/namedb/named.conf thinking that it's actually /etc/named.conf
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
Tel: +44 1628 476614 Marlow
Fax: +44 0870 0522645 Bucks., SL7 1TH UK
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020714103149.GB25158>