stakanov wrote:
So it appears it [privoxy] is running now. I eliminated the privoxy config.
Haha - the question is, does it still do what you expect it to do. With no configuration, that seems unlikely.
I did then set up privoxy as kde system proxy. But it does not work (privoxy is not used) and then I tried to set in the browser manually, but it does not work. So now it runs but still it is not used. 127.0.0.1 and 8118 as settings that is: 127.0.0.1:8118
I'm not sure what a "kde system proxy" is, but I suspect it might simply mean setting the environment variable "http_proxy'. For that to take effect, you have to restart, at least the browser, maybe logout/login too. When you say "it is not used", how do you determine that? If you want to know if it's being called, but doesn't do anything, try running "tcpdump -n -i lo port 8118" (as root). That'll show you traffic going to and from privoxy. With no configuration, I expect privoxy to listen on the default address localhost:8118, but not do anything with the traffic. -- Per Jessen, Zürich (6.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org