[Luigi Gangitano] wrote:
Hi Petter,
Thanks for your report.
I checked the resolvconf documentation and init script invocation in
squid3 is handled exactly as instructed. Since this is the standard
for resolvconf I suspect that any other service which configures
resolvconf hooks will be
Hi Petter,
Thanks for your report.
I checked the resolvconf documentation and init script invocation in squid3 is
handled exactly as instructed. Since this is the standard for resolvconf I
suspect that any other service which configures resolvconf hooks will be
affected by late /usr mount.
Il giorno 21/ott/2014, alle ore 15:41, Petter Reinholdtsen p...@hungry.com
ha scritto:
This is an issue with squid, not resolvconf. If squid is providing a
script for resolvconf to run, it need to make sure it work also if
/usr/ is a separate partition and executed before /usr/ is
[Luigi Gangitano]
The point is that if /usr needs special handling for resolvconf
scripts (which, as you say, happen to run before /usr is mounted at
startup) a fix in resolvconf would solve this issue for every
package installing resolvconf scripts.
Which fix in resolvconf did you have in
Package: squid3
Version: 3.3.8-1.2
Tags: patch
User: debian-...@lists.debian.org
Usertags: debian-edu
Hi.
I discovered this on Debian Edu, where the following line is in
/var/log/syslog shortly after the first boot of a main server:
Oct 15 09:47:23 tjener resolvconf[149]:
5 matches
Mail list logo