named in sandbox
mitch at bitblock.com
Thu May 20 23:02:56 PDT 2004
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.
> -----Original Message-----
> From: owner-freebsd-net at freebsd.org
> [mailto:owner-freebsd-net at freebsd.org]On Behalf Of Muhammad Reza
> Sent: Thursday, May 20, 2004 10:02 PM
> To: freebsd-net at freebsd.org; freebsd-questions at freebsd.org
> Subject: named in sandbox
> dear All,
> I running named in sandbox as a secondary name server with
> Named log always complain:
> named-xfer exited with signal 6 and slave zone expired for every zone
> 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
> freebsd-net at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"
More information about the freebsd-questions