This seems to be a problem with privoxy's handling of localhost during
bind.  It's not a startup ordering issue because it fails the same way
no matter when it's started.  That is, as long as no network interfaces
have ip addresses.  That seems to be the trigger.  I worked around it
by adding this privoxy-restart script to /etc/network/if-up.d/

        #!/bin/bash

        service privoxy restart

- Ryan

Attachment: signature.asc
Description: Digital signature

Reply via email to