Bug 200879 - Signal related defect in pdksh-5.2.14-30.3
Summary: Signal related defect in pdksh-5.2.14-30.3
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: pdksh
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Karsten Hopp
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: FAST4.5APPROVED
TreeView+ depends on / blocked
 
Reported: 2006-08-01 08:24 UTC by Karsten Hopp
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-06-27 14:55:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Karsten Hopp 2006-08-01 08:24:29 UTC
Description of problem:
'trap exit 1 ERR' fails with  ksh: trap: bad signal ERR

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

Additional info:
the sort parameters in siglist.sh work only for some of the signals, result is
that some signals are not sorted in the output.
sed -n 's/{ QwErTy/{/p' < $out | awk '{print NR, $0}' | sort -b -k3.3n -k 1n ...
needs to be replaced with
sed -n 's/{ QwErTy/{/p' < $out | awk '{print NR, $0}' | sort -k3n -k 1n ...

Comment 4 Matthew Roth 2006-09-20 19:25:06 UTC
I was not able to reproduce this problem in pdksh-5.2.14-30.3 on RHEL 4 Update 
3, but I do encounter this problem in pdksh-5.2.14-21.5 on RHEL 3 Update 8.  
pdksh-5.2.14-21 worked fine but then when Update 8 was applied that include 
pdksh-5.2.14-21.5 I get this error.

When will there be an update to fix pdksh-5.2.14-21.5 on RHEL 3?

Comment 5 Karsten Hopp 2006-09-28 11:47:04 UTC
re comment #4: You need to file a new bugzilla against RHEL-3. 
In the meantime try this unofficial, unsupported package:
http://people.redhat.com/karsten/pdksh-5.2.14-21.7.i386.rpm

Comment 9 Karel Volný 2007-06-27 14:55:39 UTC
this bug depends on the build environment, if systemv-style or gnu-style 
parameters are used

none of the examined packages for pdksh-5.2.14-30.3 suffers from it, so 
closing


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