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#21653 - Tinyproxy does not start with default settings
Attached to Project:
Community Packages
Opened by SanskritFritz (SanskritFritz) - Tuesday, 09 November 2010, 09:10 GMT
Last edited by Lukas Fleischer (lfleischer) - Tuesday, 09 November 2010, 09:39 GMT
Opened by SanskritFritz (SanskritFritz) - Tuesday, 09 November 2010, 09:10 GMT
Last edited by Lukas Fleischer (lfleischer) - Tuesday, 09 November 2010, 09:39 GMT
|
DetailsDescription:
The default settings in tinyproxy collide, thus tinyproxy exits immediately without any error output. In particular, these config options don't work together: User nobody Group nobody PidFile "/var/run/tinyproxy/tinyproxy.pid" LogFile "/var/log/tinyproxy/tinyproxy.log" The user 'nobody' has no write access to those folders. The solution was to create and 'chown nobody' the /var/run/tinyproxy and /var/log/tinyproxy folders. Additional info: * package version(s): tinyproxy 1.8.2-1 * config and/or log files etc. Steps to reproduce: Start tinyproxy this way: su -c "tinyproxy -d" |
This task depends upon
Closed by Lukas Fleischer (lfleischer)
Tuesday, 09 November 2010, 09:39 GMT
Reason for closing: Duplicate
Additional comments about closing: Dupe of FS#21639 . Fixed in 1.8.2-2.
Tuesday, 09 November 2010, 09:39 GMT
Reason for closing: Duplicate
Additional comments about closing: Dupe of