> Len Conrad <LConradGo2France.com> wrote:
> >bind9 runs quite nicely and easily in a chroot.
>
> Can it communicate with syslogd when chrooted?

        Yes. If it can't then it is the vendor's syslog implementation
        that is broken. Syslog and chroot are standard parts of the
        OS and they should work together. If they don't blame the
        OS not the application that tries to use them.

        Same with threads and set{e}{u,g}id.

> Can it accpet zone
> transfers and write the pid-file assuming a writable directory
> under $CHROOTHOME?

        Yes. It always could. BIND 8 required a more complete chroot
        envirionment as it exec'd named-xfer.

> What happens when you send the daemon a -HUP?

        It re-reads named.conf and acts on the changes there.

> These are all things we've had problems with under bind8. Be great
> if they are fixed.
>
> --
> Roger Marquis
> Roble Systems Consulting
> http://www.roble.com/
>
>
> To Unsubscribe: send mail to majordomoFreeBSD.org
> with "unsubscribe freebsd-security" in the body of the message

--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrewsisc.org
To Unsubscribe: send mail to majordomoFreeBSD.org
with "unsubscribe freebsd-security" in the body of the message

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]