Having to manually start privoxy makes maintenance unnecessary complex. Would be much better to add socket activation support (alongside with corresponding .socket unit) so privoxy could be started automatically on-demand by systemd. In addition this would make possible seamless upgrades when restarting privoxy does not lead to loosing any data and goes completely unnoticed by the users.
Thanks for the suggestion. In the future, please don't file
feature requests as bugs.
Anyway, most platforms Privoxy runs on don't use systemd so
this is unlikely to happen unless someone who cares about this
submits a non-invasive and maintainable patch.
An alternative here is supporting listening on UNIX sockets.
Then systemd-socket-proxyd can be used to automatically activate privoxy and redirect any connections.
Would this be an acceptable solution?
Sure. It does not solve the somone-has-to-submit-a-patch part, though.