Package: procps Version: 1:3.2.7-5 Severity: minor I've always wondered why "sudo kill $pid" wouldn't give an error if the specified process ID does not exist. I now know that's because sudo runs /bin/kill .
Now I'm wondering why /bin/kill doesn't print any error message when it fails to find the specified process ID. In fact, it never seems to print any error message, e.g. also in case of EPERM. This is quite unexpected, every kill command I've encountered on any flavour of Unix for the past 25 years will give an error message in such situations. (At least the exit status _is_ correctly set...) Please consider adding the printing of error messages when kill() fails. Thanks, Paul Slootman -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (650, 'testing'), (625, 'stable'), (600, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22.15 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages procps depends on: ii libc6 2.7-4 GNU C Library: Shared libraries ii libncurses5 5.6+20071124-1 Shared libraries for terminal hand ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip Versions of packages procps recommends: ii psmisc 22.5-1 Utilities that use the proc filesy -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
