- Overview: A new installation of tinyproxy will not start with the default configuration file because the PidFile directive is commented out and the program defaults to a non-existent location. - Steps to reproduce: Install www/tinyproxy package. Attempt to start the service. - Actual results: tinyproxy exits immediately. - Expected results: tinyproxy should start and continue running as a daemon with sensible default settings. - Additional information: Output of tinyproxy when run in debug mode from command line with the default configuration file provided by the package: # tinyproxy -d tinyproxy: Could not create file /var/run/tinyproxy/tinyproxy.pid: No such file or directory tinyproxy: Could not create PID file. Obviously, this is trivial to fix by uncommenting the PidFile directive in the provided configuration file, but it violates the principle of least astonishment.
Patch provided for bug 207051 fixes this issue as well.
Created attachment 170478 [details] Patch to update port to 1.8.4 Patch updates port to 1.8.4, and uncomments 'PidFile' and 'LogFile' directives in config file so that service can be started with default configuration after installation.
Comment on attachment 170478 [details] Patch to update port to 1.8.4 Superseded by bug 207051 -> attachment 170242 [details]
Maintainer timeout, implicit approval
Assign to committer that resolved.