Package: squid3 Version: 3.4.8-6+deb8u1 Severity: critical On a system with systemd, dnsmasq and resolvconf installed, the /etc/resolvconf/update-libc.d/squid3 hook prevents dnsmasq from starting. As far as I can see, the problem is caused by a deadlock of "systemctl start dnsmasq.service" in conjunction with "systemctl reload squid3.service". The latter one is finally called by the /etc/resolvconf/update-libc.d/squid3 hook which is invoked by dnsmasq on startup.
A possible solution might be, to check if systemd is running in the hook and calling systemctl --no-block reload squid3.service directly instead of invoke-rc.d squid3 reload Best regards, -- System Information: Debian Release: 8.2 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.20.1.amd64-smp (SMP w/1 CPU core) Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages squid3 depends on: ii adduser 3.113+nmu3 ii libc6 2.19-18+deb8u1 ii libcap2 1:2.24-8 ii libcomerr2 1.42.12-1.1 ii libdb5.3 5.3.28-9 ii libecap2 0.2.0-3 ii libexpat1 2.1.0-6+deb8u1 ii libgcc1 1:4.9.2-10 ii libgssapi-krb5-2 1.12.1+dfsg-19 ii libk5crypto3 1.12.1+dfsg-19 ii libkrb5-3 1.12.1+dfsg-19 ii libldap-2.4-2 2.4.40+dfsg-1 ii libltdl7 2.4.2-1.11 ii libnetfilter-conntrack3 1.0.4-1 ii libnettle4 2.7.1-5 ii libpam0g 1.1.8-3.1 ii libsasl2-2 2.1.26.dfsg1-13 ii libstdc++6 4.9.2-10 ii libxml2 2.9.1+dfsg1-5 ii logrotate 3.8.7-1+b1 ii lsb-base 4.1+Debian13+nmu1 ii netbase 5.3 ii squid3-common 3.4.8-6+deb8u1 squid3 recommends no packages. Versions of packages squid3 suggests: ii resolvconf 1.76.1 pn smbclient <none> pn squid-cgi <none> pn squid-purge <none> pn squidclient <none> pn ufw <none> pn winbindd <none> -- Configuration Files: /etc/resolvconf/update-libc.d/squid3 changed [not included] -- no debconf information