Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#43 start on boot in linux

2.9.x
closed-wont-fix
nobody
Other (15)
6
2002-09-03
2002-04-29
Anonymous
No

Version 2.9.14-1.6x from RPM

The documentation says to start privoxy with
/usr/sbin/privoxy /etc/privoxy/config which works fine.
Fine, that is, until you want to set it to start on
boot. When I started from a shell I had to do it as
root (most likely due to the directory permission
discussed below). After using privoxy a bit and
finding that it worked very nicely I went to try and
start it automatically. The init.d shell script uses
the user privoxy to start the process, unfortunately
the /var/log/privoxy/logfile was now owned by root and
the privoxy user could not open the file. Well for a
novice at linux this took some finding and guessing but
setting the ownership of the logfile to privoxy fixed
the problem. It would be good to include this in
documentation for those who would like to start privoxy
on boot. Better yet, could it work to include a blank
logfile in the install with the owner as privoxy? This
would eliminate the root ownership issues if you start
from the command line.

Discussion

    • labels: 412814 -->
     
  • Logged In: YES
    user_id=74317

    hard to believe that someone submitted this through the
    filter feedback system... Anyway, I thought that we
    set the directory/file permissions to privoxy.privoxy?

     
    • priority: 5 --> 6
     
    • labels: --> Other
    • milestone: --> 2.9.x
     
  • Logged In: YES
    user_id=74317

    moved to devel todos.

     
  • Hal Burgiss
    Hal Burgiss
    2002-04-29

    Logged In: YES
    user_id=322640

    With the RH rpms, the directory /var/log/privoxy is created
    owned by user privoxy. No log files are created. SuSE looks
    the same. There are instructions for how to start for both
    Redhat and SuSE that show to use the init script. This is
    only a problem if someone runs as root without the init
    script on the first time. I can't see adding this bit of
    trivia to the docs. Maybe the installer should create an
    empty logfile?

     
  • Logged In: YES
    user_id=10857

    I'll produce a workaround for it latter, but nothing will
    solve this entirely. There are many instance where even
    having this empty logfile will not help.
    IMHO, this is a "you broke, you fix" issue we should not
    have to worry about.

     
    • status: open --> closed-wont-fix
     
  • Logged In: YES
    user_id=78811

    Yes, closing.