Description of problem: Changes in Latest RHEL3.8 pdksh-5.2.14-21.5 have introduced the following reproducible problems: Problem #1 pdksh no longer supports the USR1 and USR2 Signal names. The rename fix disables using USR1 and USR2 in trap calls, must use SIGUSR1 and SIGUSR2. Other traps, INT, TERM, HUP, etc. allow the use of either the posix or the short names. > Sample program > #!/bin/ksh > trap "Echo USR1" USR1 > > Error message > > /tmp/junk[2]: trap: bad signal USR1 Problem #2 pdksh triggers the SIGTERM trap whenever a function or command call returns a non-zero value. > > Sample programs A: > > #!/bin/ksh > trap "echo got sigTERM" TERM > doit() > { > return 1 > } > doit > > Sample A output: > > got sigTERM > > > Sample programs B: > #!/bin/ksh > trap "echo got sigTERM" TERM > > ls -l /tmp/non_existing_file > > Sample B output: > > ls: /tmp/non_existing_file: No such file or directory > got sigTERM > Problem does not occur with previous RHEL3 version pdksh-5.2.14-21 Also of note: These problems do not occur on the Latest RHEL4.4 pdksh. Version-Release number of selected component (if applicable): pdksh-5.2.14-21.5 How reproducible: 100% Steps to Reproduce: 1.See above descriptions - Sample scripts 2. 3. Actual results: bad signal USR1 and TERM trap is triggered incorrectly Expected results: No bad Signal Message Program/scripts should continue Additional info:
Unfortunately this issue was not approved for inclusion in RHEL 3.9 and it is now too late as we are past Beta Freeze. Since RHEL 3.9 is the last release for RHEL 3, if you still want this issue fixed, please work with Red Hat Support and request an async errata.
Product Management has reviewed and declined this request. You may appeal this decision by reopening this request.