Bug#996738: tinyproxy: Invalid fix for bug #968322 (issue still occurs): tinyproxy exits 2 on standard systemd stop signal SIGTERM

2021-10-21 Thread RDS
Apologies, didn't notice this was a new bug. Sending only to it now. There's at least a handful of reasons why you've not see this failure when stopping other systemd-managed applications. None of which, IMO, necessarily point to or imply any weakness or shortcoming in tinyproxy's children stop

Bug#996738: tinyproxy: Invalid fix for bug #968322 (issue still occurs): tinyproxy exits 2 on standard systemd stop signal SIGTERM

2021-10-19 Thread Timo Sigurdsson
Hi again, RDS schrieb am 18.10.2021 18:42 (GMT +02:00): > Doing the dishes just now, I thought of a possible relatively simple and > "reasonable" tinyproxy-only deterministic solution: > > Add a Boolean key-pair to tinyproxy's config, call it something like > 'letHostManageStops', setting it to

Bug#996738: tinyproxy: Invalid fix for bug #968322 (issue still occurs): tinyproxy exits 2 on standard systemd stop signal SIGTERM

2021-10-19 Thread Timo Sigurdsson
P.S. Somehow the bug tracker was lost in conversation, so adding it back. Hi, thanks for taking the time to reply on this old issue. Let me respond to a couple of your remarks and statements: RDS schrieb am 18.10.2021 18:03 (GMT +02:00): > [...} > At some point in my convo with Mike I said I

Bug#996738: tinyproxy: Invalid fix for bug #968322 (issue still occurs): tinyproxy exits 2 on standard systemd stop signal SIGTERM

2021-10-17 Thread Timo Sigurdsson
Package: tinyproxy Version: 1.10.0-5 Severity: important Dear Maintainer, I installed tinyproxy on an up-to-date Debian 11.1 (bullseye) installation. I'm seeing the issue that was reported in bug #968322 and later claimed to be fixed in version 1.10.0-5 (which I run) both with the default