Hi Christopher,
Sorry for the invoke-rc.d command mistake: it was jsut a typo. Of course
you are right and the actual command there like you have said.
As for the resolvconf, it is installed on my machine:
$ apt policy resolvconf
resolvconf:
Installed: 1.79ubuntu8
Candidate: 1.79ubuntu8
Version table:
*** 1.79ubuntu8 500
500 http://pl.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
500 http://pl.archive.ubuntu.com/ubuntu artful/universe i386 Packages
100 /var/lib/dpkg/status
I would like to underline that on my Artful installation `invoke-rc.d squid
reload` somehow does not cause Squid to re-load the configuration correctly: it
is not able to go to network (although network is set up correctly) showing
instant HIER_NONE/ in the access.log.
However, like in your case there are entries in /var/log/syslog about
squid reloading:
Feb 15 19:17:39 hatchling systemd[1]: Reloading LSB: Squid HTTP Proxy version
3.x.
Feb 15 19:17:39 hatchling squid[4613]: * Reloading Squid HTTP Proxy
configuration files
Feb 15 19:17:39 hatchling squid[4613]: ...done.
Feb 15 19:17:39 hatchling systemd[1]: Reloaded LSB: Squid HTTP Proxy version
3.x.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748471
Title:
Automatic squid reload on resolv.conf update does not work
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1748471/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
