Your message dated Sun, 6 Jan 2008 12:03:30 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#299132: lwresd: fails to start due to '-u bind'; false 
alarm?
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: bind9
Severity: normal
Tags: patch

The directory /var/run/bind/run is set to root:bind by /etc/init.d/bind9

bind9 defaults to "-u bind" in /etc/default/bind9

These two settings conflict.

Simple fix is to change the chmod to set the user, as well:

--- /etc/init.d/bind9.old       2005-03-11 19:14:08.000000000 -0500
+++ /etc/init.d/bind9   2005-03-11 19:04:13.000000000 -0500
@@ -19,7 +19,7 @@
        # dirs under /var/run can go away on reboots.
        mkdir -p /var/run/bind/run
        chmod 775 /var/run/bind/run
-       chown root:bind /var/run/bind/run >/dev/null 2>&1 || true
+       chown bind:bind /var/run/bind/run >/dev/null 2>&1 || true

        if [ ! -x /usr/sbin/named ]; then
            echo "named binary missing - not starting"


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (900, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)


--- End Message ---
--- Begin Message ---
Version: 9.3.0-1

Actually fixed in bind 9.2.5beta2

lamont


--- End Message ---

Reply via email to