OpenRC relies on PidFile value to detect that service is running. By default, this option is commented out, and OpenRC marks tinyproxy service as crashed: /etc/init.d/tinyproxy start tinyproxy | * Starting tinyproxy ... /etc/init.d/tinyproxy status * status: crashed
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=27231d632f1c4ba2d3f8e18ee85530f64e0d3ace commit 27231d632f1c4ba2d3f8e18ee85530f64e0d3ace Author: Azamat H. Hackimov <azamat.hackimov@gmail.com> AuthorDate: 2025-02-12 20:23:07 +0000 Commit: Ben Kohler <bkohler@gentoo.org> CommitDate: 2025-02-27 18:53:18 +0000 net-proxy/tinyproxy: enable PidFile option by default OpenRC relies on PidFile value to detect that service is running. By default, this option is commented out, and OpenRC marks tinyproxy service as crashed. Applied upstream patch that define @runstatedir@ (/run) for for PID file instead of @localstatedir@ (/var). Closes: https://bugs.gentoo.org/949682 Signed-off-by: Azamat H. Hackimov <azamat.hackimov@gmail.com> Signed-off-by: Ben Kohler <bkohler@gentoo.org> .../files/tinyproxy-1.11.2_use-runstatedir.patch | 89 ++++++++++++++++++++++ net-proxy/tinyproxy/tinyproxy-1.11.2-r1.ebuild | 83 ++++++++++++++++++++ 2 files changed, 172 insertions(+)
