I can confirm this bug after the latest update of sid, it seems to be caused by a lack of DNS server response (although in my case maradns appears to start earlier in the boot process, probably it isn't "ready" to answer queries?)... There are also issues with apache2 and other daemons that depend on DNS to start. However, I believe this should be reassigned as it's not a bug with privoxy but with insserv and/or the ordering algorithm.
Regards, -- Mihnea-Costin Grigore -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
