#854 Privoxy on OS X will not start

version 3.0.19
closed-fixed
5
2012-03-13
2012-03-11
Anonymous
No

I just installed privoxy on OS X 10.6 and it wouldn't start, although launchctl thought it did. The reason was that the config file looks for the default files in . and it cannot find them.

My workaround was to add "/usr/local/etc/privoxy" as the working directory in /Library/LaunchDaemons/org.ijbswa.privoxy.plist
Alternatively one could change the /usr/local/etc/privoxy/config

Discussion

  • Ian Silvester

    Ian Silvester - 2012-03-11

    Hi,

    Yes, a tester notified me of this fault just yesterday; it affects only vanilla installs. I intend to release a corrected installer (correcting the omission in the config file) later today.

    Many thanks,

    Ian

     
  • Ian Silvester

    Ian Silvester - 2012-03-11
    • summary: Privoxy will not start --> Privoxy on OS X will not start
     
  • Ian Silvester

    Ian Silvester - 2012-03-13

    Hi,

    This bug has been fixed in the release now available in the Files section of the project.

    Cheers,

    Ian

     
  • Ian Silvester

    Ian Silvester - 2012-03-13

    [canned message]

    I think this is a manifestation of the "100% CPU" problem. What
    happens is some site has massive amounts of whitespace in their
    HTML that you don't ultimately see, but Privoxy spends a lot of
    time trying to filter it all. The interim solution is to keep
    Privoxy from filtering that particular site in the user.action
    file. Of course, once Privoxy starts spinning, it'll need to be
    killed and restarted.

    The problem is in the js-annoyances and the unsolicited-popups
    filters. If you turn those off in general (or for your problem
    site(s) in particular) I think you'll have better luck. Can you
    please give that a try?

     
  • Ian Silvester

    Ian Silvester - 2012-03-13
    • assigned_to: nobody --> diem
    • status: open --> closed-fixed
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks