Bug 240822 - ksh not understanding named kill signals
ksh not understanding named kill signals
Status: CLOSED DUPLICATE of bug 200148
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: pdksh (Show other bugs)
3.8
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Smetana
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-05-21 22:33 EDT by Patrick Clohessy
Modified: 2007-11-16 20:14 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-06-06 05:33:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Patrick Clohessy 2007-05-21 22:33:50 EDT
Description of problem:

Latest version of ksh does not understand the named kill signal, TERM.

Latest version - pdksh-5.2.14-21.5
Output from kill -l
15   15 Terminated 

Previous version I was using - pdksh-5.2.14-21
Output from kill -l
15   TERM Terminated

Infact, most of the signals are no longer named in the latest ksh.

Version-Release number of selected component (if applicable):

pdksh-5.2.14-21.5

How reproducible:

Try to trap TERM signals then run a command with a non-zero exit status.

Steps to Reproduce:
1. Create a ksh script as follows

#!/bin/ksh

trap 'echo "TRAP"' TERM
ls -la /tmp/file_that_doesnt_exist
echo $?

  
Actual results:
ls: /tmp/file_that_doesnt_exist: No such file or directory
TRAP
1

Expected results:
ls: /tmp/file_that_doesnt_exist: No such file or directory
1

Additional info:
Comment 1 Tomas Smetana 2007-05-23 08:43:52 EDT
This looks to be a duplicate of
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=200148.
Comment 2 Tomas Smetana 2007-06-06 05:33:21 EDT

*** This bug has been marked as a duplicate of 200148 ***

Note You need to log in before you can comment on or make changes to this bug.