FS#54570 : privoxy bad systemd configuration

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!

FS#54570 - privoxy bad systemd configuration

Attached to Project: Community Packages
Opened by solar archigo (archigo) - Saturday, 24 June 2017, 14:13 GMT
Last edited by Christian Rebischke (Shibumi) - Saturday, 22 February 2020, 20:32 GMT

Task Type	Bug Report
Category	Packages
Status	Assigned Reopened
Assigned To	Lukas Fleischer (lfleischer)
Architecture	All
Severity	Low
Priority	Normal
Reported Version
Due in Version	Undecided
Due Date	Undecided
Percent Complete
Votes	0
Private	No

Details

Description:

privoxy does not log into /var/log/privoxy/logfile with the current systemd privoxy.service configuration,
even if it's enabled in the /etc/privoxy/config. It logs to journal.

Something like:

[Service]
#User=privoxy
#Type=simple
#ExecStart=/usr/bin/privoxy --no-daemon /etc/privoxy/config
#PrivateDevices=yes

Type=forking
PIDFile=/run/privoxy.pid
ExecStart=/usr/bin/privoxy --pidfile /run/privoxy.pid --user privoxy.privoxy /etc/privoxy/config
ExecStop=/usr/bin/rm /run/privoxy.pid
SuccessExitStatus=15

is needed.

Additional info:
* package version(s)
all
* config and/or log files etc.

Steps to reproduce:

config:
logdir /var/log/privoxy
logfile logfile
# log destination request
debug 1024

This task depends upon