Date: Tue, 5 Oct 2004 17:11:16 -0700 (PDT) From: Doug Barton <DougB@FreeBSD.org> To: Tillman Hodgson <tillman@seekingfire.com> Cc: freebsd-current@freebsd.org Subject: Re: HEADS UP: named now runs chroot'ed by default Message-ID: <20041005170720.M3095@bo.vpnaa.bet> In-Reply-To: <20040930153801.GP35869@seekingfire.com> References: <20040928025635.Q5094@ync.qbhto.arg> <200409291951.12610.peter@wemm.org> <43039.193.35.129.161.1096541075.squirrel@webmail.xtaz.net> <20040930153801.GP35869@seekingfire.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 30 Sep 2004, Tillman Hodgson wrote:
> How does chroot and NFS interact?
It is theoretically possible, but I would not do it for performance and
reliability reasons. If you are doing something useful with named on a
real network you will have enough variables that you cannot control
which will make your life difficult, I personally would not want to add
more pain to the mix that could be avoided. :)
If you want to share configs, share data, etc; then rsync, scp, etc. are
your friends. When I was at Yahoo! we had all the essential files in a
central CVS repo and I used makefiles with various targets to push them
out to the servers. This made updates, replication, installation, etc.
very easy with almost no room for error, and no external dependencies
other than the network and power for the individual name server.
Hope this helps,
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041005170720.M3095>