On Thu, 01 Dec 2016 20:41:57 -0500 Stefan Monnier wrote:
> > 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.ser
> 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". Th
Just ran into this bug. The resolvconf hook is indeed run after
dnsmasq is up and running. When I run `sudo systemctl start dnsmasq`
from a terminal, it doesn't return, and running `systemctl` from
another terminal reveals
dnsmasq.service loaded activating start-post start dnsmasq - A
lightweight
tags severity important
On Mon, 14 Sep 2015 11:11:45 +0200 Patrick Cernko wrote:
>
> On a system with systemd, dnsmasq and resolvconf installed, the
> /etc/resolvconf/update-libc.d/squid3 hook prevents dnsmasq from
> starting.
That hints that the dnsmasq startup sequence is being done the wrong w
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 conj
5 matches
Mail list logo
