When Dansguardian is configured to use squid, running on the same machine, as another proxy behind it, it fails to start on boot because squid has not yet started. Reproducible: Always Steps to Reproduce: 1. Emerge dansguardian 2. Set "proxyip" and "proxyport" to point to the squid proxy running on the same machine. 3. "rc-update add dansguardian default" 4. reboot Actual Results: dansguardian fails to start on reboot because it's attempting to connect to a squid that isn't running yet. Expected Results: It should wait to start until after squid is running and then it will start successfully. To fix it I put a "after squid" in the depend() function of the dansguardian init script.
I can confirm this bug. I solved it by putting "provide proxy" in squid's init script, and "need net proxy" in dansguardian's. Since dansguardian can use other proxies than squid, I consider this a better approach than "after squid", although it requires all proxy servers init script to have "provide proxy" for this to be useful. But it has to start somewhere, right? :)
I was able to correct this behavior by adding 'squid' to /etc/init.d/dansguardian: depend() { need net squid }
fixed in 2.8.0.4
*** Bug 83407 has been marked as a duplicate of this bug. ***
