severity 468363 normal
tag 468363 patch
found 468363 1:3.2.7-6
thanks
On Thu, Feb 28, 2008 at 04:14:02PM +0100, Paul Slootman wrote:
> 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 for the report, that's bothered me too but I've never
investigated further than the use of /bin/kill until now. Just adding
perror helps.
--- procps-3.2.7.orig/skill.c
+++ procps-3.2.7/skill.c
@@ -309,6 +309,7 @@
pid = strtol(argv[argc],&endp,10);
if(!*endp){
if(!kill((pid_t)pid,signo)) continue;
+ perror("kill");
exitvalue = 1;
continue;
}
BTW (Craig) you seem to have included a spurious unused
(already-applied) patch file in the diff.gz:
procps-add-lsb-logging.patch?bug=384920;msg=5;att=1
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
