bin/40282: [patch] kill(1) has bad error checking for command
jilles at stack.nl
Sat Nov 7 15:30:04 UTC 2009
The following reply was made to PR bin/40282; it has been noted by GNATS.
From: Jilles Tjoelker <jilles at stack.nl>
To: bug-followup at FreeBSD.org, oleg at reis.zp.ua
Subject: Re: bin/40282: [patch] kill(1) has bad error checking for command
Date: Sat, 7 Nov 2009 16:21:46 +0100
I think the idea of aborting on syntax errors makes sense, but aborting
on a kill(2) error seems to go too far. I have found various shells
(tcsh, real ksh) that stop processing a kill builtin if they encounter
an invalid pid (if there were any previous valid pids, signals will have
been sent), but have not found any that stop processing if a kill(2)
returns an error.
By the way, do not imply anything about command behaviour from
/usr/bin/which. sh(1) and bash(1) do not have a which(1) builtin, so
/usr/bin/which will be used, which does not know about shell builtins.
It just happens to be the case that sh(1) does not have a kill builtin
(although that may change in the future) and bash's kill builtin handles
errors the same way as our /bin/kill. You can use 'type' for accurate
information in these shells.
More information about the freebsd-bugs