Control: severity -1 important On Do 13 Aug 2020 01:02:26 CEST, RDS wrote:
Package: tinyproxy Version: 1.10.0-2+deb10u1The default systemd stop signal (SIGTERM) on Buster machines cause tinyproxy to exit 2, which systemd then logs and reports as a tinyproxy failure. This is happening consistently on both a 32-bit and two 64-bit machines, at least after a first systemd stop of tinyproxy, which often (?never?) reports an exit failure, but does after each subsequent start-stop cycle.Not sure where the root cause might be. Thought it best to let packaging (systemd) people consider it first.Don't know if this is appropriate, but here's a solution that does not require any tinyproxy code changes. I've not examined its code to confirm this change is safe, but I've been using it without issue.
[...]
$ sudoedit /usr/lib/systemd/system/tinyproxy.service # Add line 'KillSignal=SIGINT' to [Service] section.
This should rather be fixed in the tinyproxy code. I also sense this is an important bug, so raising severity. Will look into it (but patches welcome).
Mike -- DAS-NETZWERKTEAM c\o Technik- und Ökologiezentrum Eckernförde Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde mobile: +49 (1520) 1976 148 landline: +49 (4351) 850 8940 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de
pgp1Q24y3uvLN.pgp
Description: Digitale PGP-Signatur
