Package: bind9
Version: 1:9.9.5.dfsg-9
Severity: normal

the source is configured with --localstatedir=/var, which causes bind
to try writing to /var/run. The following configuration directives are
needed in named.conf.options to make error messages vanish from the
log on startup:

        session-keyfile "/run/named/session.key";
        pid-file "/run/named/named.pid";

Without those, bind tries writing the session-keyfile to
/var/run/named/session.key and tries to create /run/named for a
pidfile which is then not written since in the systemd world, bind
gets started with -f which does not create a pidfile.

This is not a problem in a non-chrooted environment since
/var/run/named exists in such environments. In a chroot, /var/run does
not necessarily exist.

If the configure script has a --rundir option, it should be explicitly
set to /run. If it does not, the options given above should be part of
the configuration.

Greetings
Marc


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to