Date: Thu, 20 May 2004 23:02:46 -0700 From: "Mitch (bitblock)" <mitch@bitblock.com> To: "Muhammad Reza" <reza@mra.co.id>, freebsd-net@freebsd.org, freebsd-questions@freebsd.org Subject: RE: named in sandbox Message-ID: <OCEGLFACMGOKINMEOKANGEBPDBAA.mitch@bitblock.com> In-Reply-To: <40AD8D44.5020508@mra.co.id>
next in thread | previous in thread | raw e-mail | index | archive | help
You need to compile named-xfer as statically linked, or move it's dependant libraries into the chroot. Can't remember the details of how I did that, and I don't use named any more - but that's your problem. hope that helps. m/ > -----Original Message----- > From: owner-freebsd-net@freebsd.org > [mailto:owner-freebsd-net@freebsd.org]On Behalf Of Muhammad Reza > Sent: Thursday, May 20, 2004 10:02 PM > To: freebsd-net@freebsd.org; freebsd-questions@freebsd.org > Subject: named in sandbox > > > dear All, > > I running named in sandbox as a secondary name server with > FreeBSD-5.1.p17, > Named log always complain: > named-xfer exited with signal 6 and slave zone expired for every zone > transfer. > but, when it's running on default mode (no chroot sandbox) or as a > primary server (with chroot sandbox). named work fine. > please help me , how to make secondary zone transfer running in sandbox > > regards > reza > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?OCEGLFACMGOKINMEOKANGEBPDBAA.mitch>