privoxy won't start

mcg · n00b Joined: 03 Jan 2006 Posts: 3

hi

i can not make the privoxy work

privoxy user and group exist

/var/log/privoxy belong to user privoxy and group privoxy
/etc/privoxy belong to user privoxy and group privoxy

when i start /etc/init.d/privoxy start it won't start.config file is exist and belong to privoxy and i only added to config forward-socks4a / localhost:9050 .

when i run as root it runs, but i do't want to run it as root. i tried to run it from /etc/privoxy with command privoxy --pidfile /var/run/privoxy.pid --user privoxy.privoxy it complained that "fatal /etc/privoxy/config permission denied" this is insane all files belog to privoxy and readable plus writeable.what else should i try?can anyone help please?thanks

kommissar · Tux's lil' helper Joined: 19 May 2005 Posts: 78

You should start privoxy using '/etc/init.d/privoxy start' as root. It should drop to the proper user/group automatically.

PaulBredbury · Watchman Joined: 14 Jul 2005 Posts: 7310

Check this thread.

mcg · n00b Joined: 03 Jan 2006 Posts: 3

PaulBredbury · Watchman Joined: 14 Jul 2005 Posts: 7310

mcg · n00b Joined: 03 Jan 2006 Posts: 3

success to cd /etc/privoxy & command cat config without any problem

cbpowell · n00b Joined: 27 Mar 2004 Posts: 2

On a new machine installation I was having weird "permission denied" problems with multiple programs, including sudo and privoxy. The issue was the permission setting of /.

codadilupo · Advocate Joined: 05 Aug 2003 Posts: 3135

I also have the same permission on /.
I think those permissions are less relaxed than 755, and I would like to maintain them (it's a server).
What I cannot understand is why only privoxy doesn't work.

I start apache, and it works.
I start tor, and it works.
I start cups, and it works.
I start ssh and it works.

Now, form that all of this daemons have their conf files in /etc/$daemon_name/ ...

Why only privoxy seems to be unable to read its config file...

Coda

PaulBredbury · Watchman Joined: 14 Jul 2005 Posts: 7310

Run su - privoxy, then have a look around the filesystem to see what the privoxy user has access to.

Edit: For su to work, you'd need to change the privoxy line in /etc/passwd from /bin/false to /bin/sh

pietinger · Posted: Thu Mar 06, 2008 6:53 pm Post subject:

Hi,

I had the same problem today. AND Privoxy was running without a problem before.

What I did ? I copied /etc with "unison" to another PC. And I made a little mistake with the result that the permission for /etc was wrong after.

So check the permissions for /etc also !