Package: sniproxy Version: 0.6.0-2 Severity: important X-Debbugs-Cc: cypr...@octopuce.fr
Dear Maintainer, The provided systemd unit does not handle correctly the daemon life cycle. After starting sniproxy with systemd, the unit enters the inactive dead state. systemctl status sniproxy reports that some PID are still associated but detached. As such, systemctl restart sniproxy does not kill the remaining processes. We we're able to obtain a normal systemd behavio by adding the -f flag to the ExecStart command of the systemd unit (which prevent sniproxy from forking to the background). Our current override (generated using systemctl edit sniproxy) contains: [Service] ExecStart= ExecStart=/usr/sbin/sniproxy -f And then the daemon can be managed fully using systemctl. Thanks, -- System Information: Debian Release: 11.5 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-21-amd64 (SMP w/8 CPU threads) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages sniproxy depends on: ii init-system-helpers 1.60 ii libc6 2.31-13+deb11u4 ii libev4 1:4.33-1 ii libpcre3 2:8.39-13 ii libudns0 0.4-1+b1 ii lsb-base 11.1.0 Versions of packages sniproxy recommends: ii logrotate 3.18.0-2+deb11u1 sniproxy suggests no packages. -- no debconf information
