FS#54570 - [privoxy] bad systemd configuration - logging

Attached to Project: Community Packages
Opened by solar archigo (archigo) - Saturday, 24 June 2017, 14:13 GMT
Last edited by Brett Cornwall (ainola) - Sunday, 29 January 2023, 08:00 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Brett Cornwall (ainola)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
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

Closed by  Brett Cornwall (ainola)
Sunday, 29 January 2023, 08:00 GMT
Reason for closing:  No response
Comment by Doug Newgard (Scimmia) - Tuesday, 27 June 2017, 05:26 GMT
Sounds more like an upstream issue
Comment by guggi (guggo) - Tuesday, 11 February 2020, 22:39 GMT
solution:

https://unix.stackexchange.com/questions/421104/privoxy-isnt-saving-to-logfile/442928#442928
Comment by freswa (frederik) - Tuesday, 11 February 2020, 22:43 GMT
Though this issue is pretty old, don't we want to get the service file straight?
Seems like a reasonable request to me.
Comment by Toolybird (Toolybird) - Tuesday, 06 December 2022, 06:41 GMT
Dupe  FS#61464 
Comment by Brett Cornwall (ainola) - Monday, 16 January 2023, 01:52 GMT
At first glance, I agree with Scimmia: This seems more like an upstream issue. I don't think we should hardcode the logfile in the systemd unit as a) someone might want a different file name and b) Not everyone wants a file. Upstream should properly output logging contents when configured in the config file, shouldn't they?

I feel like I might be missing something, though: Why does the example change so many things?

Loading...