[Resolvconf-devel] Bug#479867: resolvconf vs. down djbdns(dnscache) service

Soeren Sonnenburg bugreports at nn7.de
Wed May 7 04:52:18 UTC 2008


Package: resolvconf
Version: 1.40
Severity: important
Tags: patch

when one has djbdns installed and its dnscache configured as forwared
(but marked down), then resolvconf will try to restart dnscache even if it
is down and fail.  The reason is in /etc/resolvconf/update.d/dnscache
 and the fix is to add a [ ! -f "$SVC/down" ] to the if like here:


                        if \
                                [ -d "$SVC" ] \
                                && [ -f "$SVC/run" ] \
                                && [ ! -f "$SVC/down" ] \
                                && [ -d "$SVC/root" ] \
                                && [ -d "$SVC/root/servers" ] \
                                && [ -d "$SVC/root/ip" ] \
                                && [ -s "$SVC/env/FORWARDONLY" ] \
                                && grep -q dnscache "$SVC/run"
                        then


-- System Information:
Debian Release: lenny/sid
  APT prefers stable
  APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-sonne (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages resolvconf depends on:
ii  coreutils                     6.10-6     The GNU core utilities
ii  debconf [debconf-2.0]         1.5.21     Debian configuration management sy
ii  lsb-base                      3.2-12     Linux Standard Base 3.2 init scrip

resolvconf recommends no packages.

-- debconf information excluded





More information about the Resolvconf-devel mailing list