Regardless of resolvconf or dnsmasq, squid itself takes about 30s to
restart. I wonder if it depends on dnsmasq via nss-lookup, then when
dnsmasq is restarted, that tries to restart squid, which takes 30s each
time? I couldn't reproduce the "squid reload" blocking when I run it
manually, but I do s
This is complicated indeed. I also spotted this in the logs during the long
wait:
Oct 25 21:16:07 xenial-squid-dnsmasq systemd[1]: nss-lookup.target: Job
nss-lookup.target/start failed with result 'dependency'.
and nss-lookup.target has something related to dnsmasq:
root@xenial-squid-dnsmasq:~#
** Also affects: fetchmail (Ubuntu Cosmic)
Importance: High
Assignee: Karl Stenerud (kstenerud)
Status: Fix Committed
** Changed in: fetchmail (Ubuntu Cosmic)
Status: Fix Committed => In Progress
** Also affects: fetchmail (Ubuntu Bionic)
Importance: Undecided
Stat
