Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#10617 - [privoxy 3.0.8] /var/spool/privoxy does not exist

Attached to Project: Arch Linux
Opened by solsTiCe (zebul666) - Monday, 09 June 2008, 08:26 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 03 November 2009, 18:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andrea Scarpino (BaSh)
Architecture All
Severity Very Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No


i got this error or warning, daily, in my cron mail
user privoxy: directory /var/spool/privoxy does not exist

and when i look at /etc/passwd i see that user privoxy has /var/spool/privoxy as its home directory

either create that directory (/var/spool/privoxy) or either choose another directory

Additional info:

Steps to reproduce:
install the package and run pwck -r
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Tuesday, 03 November 2009, 18:18 GMT
Reason for closing:  Fixed
Additional comments about closing:  privoxy-3.0.12-3
Comment by Dave (DaveCode) - Friday, 22 August 2008, 09:29 GMT
Latest upstream version is currently 3.0.10 stable.

Missing folders/users/groups/permissions is a generic problem with this package. Some rc.d work attached for package team, freely use/abuse/ignore/adopt/plagiarize/debug/distribute.
Comment by Dave (DaveCode) - Friday, 22 August 2008, 10:18 GMT
To validate upstream source tarball, import these keys.
gpg --keyserver hkp:// --search-keys fabiankeil
Comment by Dave (DaveCode) - Saturday, 23 August 2008, 01:14 GMT
Arch can assign user "privoxy" to group "nobody"
Debian does exactly this, it uses

Which seems better than a special group for one program.

I also wish Arch would not add log rotation cron jobs, or prompt for them during install, as an optional feature.
Comment by Dave (DaveCode) - Saturday, 23 August 2008, 10:49 GMT
Updated script - works fine. Changes: No need to pre-create log/jar files, only logdir, which needs permissions set as given. Could therefore strip down the script. Upstream source comments note hacks on logging startup. Upstream had fatal bugs in a user file, too (patch included).
Comment by Noel Maersk (veox) - Tuesday, 12 May 2009, 22:01 GMT
Still present in 3.0.12.

I say against using 'nogroup', it would be a security risk: random programs that, too, would happen to be in this group could then get read/write permission to configuration files.
Comment by Xyne (Xyne) - Saturday, 05 September 2009, 14:03 GMT
Has there been any progress towards resolving this? Would it be possible to simple create and delete that directory using a pre- and post-install functions?