It seems like the start-stop-daemon uses /proc/pid/stat to find the matching process name like 'pgrep' does it.
The man page of 'pgrep' describes the limitation: NOTES The process name used for matching is limited to the 15 characters present in the output of /proc/pid/stat. Use the -f option to match against the complete command line, /proc/pid/cmdline. For the postgrey init script this behaviour of start-stop-daemon renders it unusable. The only functions working is "start" and "restart" - that's not enough. So we can work around this like Nye Liu did. We even can completely ommit the "--name" option leaving the risk of killing the wrong process. Or we can just use "postg" as search pattern. start-stop-daemon does not expect the full path, it's just only able of recongnizing the first 15 characters (see pgrep limitation). The finest solution will be, if the start-stop-daemon could the able to match on /proc/pid/cmdline, like pgrep does if choosen the "-f" switch. Perhaps we should file another bug at the dpkg package? Searching for i just found one similiar bug: start-stop-daemon: --exec should also check the first argument of /proc/PID/cmdline https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=202719 But in the meanwhile the init script of postgrey should be fixed without relying on start-stop-daemosn limitations. regards, Matthias -- Matthias Wamser, Senior Systems Engineer, mailto: m...@ilk.net ILK Internet GmbH, Am Sandfeld 15, D-76149 Karlsruhe Tel: +49 (0) 721 9100 0, http://www.ilk.net Geschaeftsfuehrer Matthias Felger, AG Mannheim, HRB 107037 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
