Gustav Degreef wrote:
So run "privoxy --no-daemon <configfile>". There doesn't seem to be a debug options. If that doesn't get privoxy running, there's bound to be error messages of some sort.
/Per
Thanks, Per, that started it. The output is:
That's great - we're making progress.
privoxy --no-daemon /etc/privoxy/config Jun 06 21:47:49 Privoxy(b7d496c0) Info: loading configuration file '/etc/privoxy /config': Jun 06 21:47:49 Privoxy(b7d496c0) Info: Privoxy version 3.0.6 Jun 06 21:47:49 Privoxy(b7d496c0) Info: Program name: privoxy Jun 06 21:47:49 Privoxy(b7d496c0) Info: Listening on port 8118 for local connect ions only
So it looks like it's running just fine?
Can you give me a pointer what to do now to start it automatically? The information from the Suse SDB page said that one had to edit /etc/init.d scripts. At that point I was in way over my head, and perhaps I still am. The tutorial I read made is seem so easy, perhaps it's not. Anyway thanks for your help. Gustav
If the init-script (/etc/init.d/privoxy) doesn't start the daemon the way you did above, you probably need to amend the sysconfig - I don't have privoxy installed myself, but I'm guessing it will have a /etc/sysconfig/privoxy file with some configuration items that will determine how it is started at boot-time. What happens if you just do "rcprivoxy start"? /Per -- Per Jessen, Zürich (16.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org