Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
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!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
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#3908 - Cleanups to Privoxy
Attached to Project:
Arch Linux
Opened by Kurt Basil Cox (basilburn) - Monday, 06 February 2006, 02:47 GMT
Last edited by Dale Blount (dale) - Tuesday, 07 March 2006, 21:50 GMT
Opened by Kurt Basil Cox (basilburn) - Monday, 06 February 2006, 02:47 GMT
Last edited by Dale Blount (dale) - Tuesday, 07 March 2006, 21:50 GMT
|
DetailsJust a few necessary cleanups for the privoxy PKGBUILD, rc script and install file.
a) It especially needs a logrotate script as the log files fill up very quickly. b) In the PKGBUILD, userdel removes exim user instead of privoxy user. c) The options in the rc script are split into a conf.d script plus redirecting stderr to /dev/null d) The log file should probably be created with 660 permissions |
This task depends upon
Closed by Jürgen Hötzel (juergen)
Tuesday, 14 March 2006, 15:56 GMT
Reason for closing: Implemented
Additional comments about closing: Thanks for your contribution.
Tuesday, 14 March 2006, 15:56 GMT
Reason for closing: Implemented
Additional comments about closing: Thanks for your contribution.
PKGBUILD
Please find new attachements with the final changes.
/etc/cron.daily/shadow complains about Privoxy, because the install script adds a privoxy user with /var/spool/privoxy homedir but the package doesn't contain that directory.
Regarding b) from above comment: Does every packager assign UIDs/GIDs for daemon packages as he sees fit, or is there any common policy for this? (I hope so)
My latest attachment should create the user = privoxy with homedir = / similar to the user - nobody.
regarding b) privoxy needs the privoxy user to build, and by default it runs as the privoxy user as well. It wasn't arbitrary assignment by the packager. One would have to hack the privoxy's build system to change it - not really worth it.
The removal of the exim user is by mistika as basilburn mentioned.
@basilburn: Thanks for your contribution. I will use them in the next release.
Jürgen