Hide Forgot
+++ This bug was initially created as a clone of Bug #691850 +++ Description of problem: When the ksh built-in kill is called with a very large, non-existent PID value, it's treated like -1 (kill all processes owned by the user). Version-Release number of selected component (if applicable): 20080202-14.el5 How reproducible: Every time Steps to Reproduce: 1.Start a ksh session 2.Run a command like "kill 11269117401228512356" Actual results: All processes owned by the user are killed, like the -1 argument would normally do. Expected results: error message - "kill: 11269117401228512356: no such process" Additional info: We encountered this when a user was trying to kill a series of processes. The user mis-entered the process list without separating spaces. --- Additional comment from mhlavink on 2011-05-04 04:12:19 EDT --- reproducible --- Additional comment from mhlavink on 2011-05-04 04:15:26 EDT --- Created attachment 496723 [details] patch to fix this
when checking test plan for ksh, I've found a regression: this fix caused ksh regression: $ ksh -c 'kill %' Segmentation fault (core dumped)
ok, this regression does not happen with ksh version we have in RHEL-6
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1647.html