I did some further investigation of the problem and I detected the file /etc/resolvconf/update-libc.d/squid. This file is intended to solve the issue, but it does not. Why? You will find the command "restart squid" in it. But that command will fail. Changing it to "start squid" will solve the issue and not only for network manager. Anyway: shouldn't the script be located in /etc/resolvconf.d/update-libc.d/ instead of /etc/resolvconf/update-libc.d/?
Squid3 is thus not affected, because there is another resolvconf.d script that solves the issue.
Hi together,
I did some further investigation of the problem and I detected the file /etc/resolvconf /update- libc.d/ squid. This file is intended to solve the issue, but it does not. Why? You will find the command "restart squid" in it. But that command will fail. Changing it to "start squid" will solve the issue and not only for network manager. Anyway: shouldn't the script be located in /etc/resolvconf .d/update- libc.d/ instead of /etc/resolvconf /update- libc.d/ ?
Squid3 is thus not affected, because there is another resolvconf.d script that solves the issue.
I'll attach the new file.
Greetings, Tobias