For what it's worth, this does not happen with the squid-deb-proxy package (which uses squid with an optimized config) - at least after several boot processes.
The init/start script is different, for example, it uses
"start on (local-filesystems and net-device-up IFACE!=lo)"
instead of
"start on runlevel [2345]".
For what it's worth, this does not happen with the squid-deb-proxy package (which uses squid with an optimized config) - at least after several boot processes.
The init/start script is different, for example, it uses
"start on (local-filesystems and net-device-up IFACE!=lo)"
instead of
"start on runlevel [2345]".