Bug 1147526

Summary: Incorrect message printed when su is killed
Product: Red Hat Enterprise Linux 7 Reporter: Paulo Andrade <pandrade>
Component: util-linuxAssignee: Karel Zak <kzak>
Status: CLOSED ERRATA QA Contact: Tomas Dolezal <todoleza>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: jscotka, pbokoc, todoleza, vanhoof
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: util-linux-2.23.2-23.el7 Doc Type: Bug Fix
Doc Text:
* The su command was incorrectly evaluating exit statuses of its child processes. This caused it to input an incorrect messsage, "Killed (core dumped)", when a child process was killed. With this update, su prints the correct message, "Killed", when its child process is killed.
Story Points: ---
Clone Of:
: 1243877 (view as bug list) Environment:
Last Closed: 2015-11-19 12:19:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1133060, 1147532, 1243877    

Description Paulo Andrade 2014-09-29 13:12:32 UTC
Pach has been submitted upstream:
http://marc.info/?l=util-linux-ng&m=141184467317500&w=2

To repeat the problem:

terminal 1$  sudo su -
terminal 1$  echo $$

terminal 2$  kill -9 THE-PID-OF-THE-SU-IN-TERMINAL-1


It should only print "Killed", not "Killed (core dumped)"

The patch may be slightly customized to avoid needing an
extra internationalization for " (core dumped)", that is,
with a leading " ".

The patch just reorded the assignment of status, so it
only changes the text print.

Comment 6 errata-xmlrpc 2015-11-19 12:19:37 UTC
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.

https://rhn.redhat.com/errata/RHBA-2015-2093.html