Date: Thu, 30 Sep 2004 09:38:01 -0600 From: Tillman Hodgson <tillman@seekingfire.com> To: freebsd-current@freebsd.org Subject: Re: HEADS UP: named now runs chroot'ed by default Message-ID: <20040930153801.GP35869@seekingfire.com> In-Reply-To: <43039.193.35.129.161.1096541075.squirrel@webmail.xtaz.net> References: <20040928025635.Q5094@ync.qbhto.arg> <200409291951.12610.peter@wemm.org> <20040930033351.M57326@ync.qbhto.arg> <43039.193.35.129.161.1096541075.squirrel@webmail.xtaz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 30, 2004 at 11:44:35AM +0100, Matt Smith wrote: > Another quick question about this. I run the ports version of bind9 > however I still leave all the base stuff installed during installworld as > one day I might want to use it. All I do is add the following in rc.conf: > > named_enable="YES" > named_program="/usr/local/sbin/named" > named_flags="-c /usr/local/etc/named/named.conf -u bind" > > and all my zone files and pid files etc are in /usr/local/etc/named. I do this as well, though I have one extra wrinkle: /usr/local/etc/named is a RO NFS mount. How does chroot and NFS interact? -T -- Page 6: Unix is easy to use, but difficult to learn. - Harley Hahn, _The Unix Companion_
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040930153801.GP35869>