Bug 1019334 - ksh monitor mode documented contrary to what it actually does
Summary: ksh monitor mode documented contrary to what it actually does
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ksh
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Michal Hlavinka
QA Contact: Martin Kyral
URL:
Whiteboard:
Depends On:
Blocks: 2071656
TreeView+ depends on / blocked
 
Reported: 2013-10-15 13:56 UTC by Martin Kyral
Modified: 2022-04-04 13:52 UTC (History)
3 users (show)

Fixed In Version: ksh-20120801-16.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1100215 2071656 (view as bug list)
Environment:
Last Closed: 2014-10-14 07:04:13 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1381 0 normal SHIPPED_LIVE ksh bug fix update 2014-10-14 01:28:24 UTC

Description Martin Kyral 2013-10-15 13:56:44 UTC
Description of problem:

on ksh-20120801-9.el6:
ksh -m test.ksh -> xterms survive the script
ksh test.ksh -> xterms die with the script

However, the man page says contrary: "The INT and QUIT signals for an invoked command are ignored if the command is followed by & and the monitor option is not active."

This seems to be documentation bug as:
1) the ksh monitor mode behavior has been discussed with David Korn
2) bash man page says: "...keyboard-generated signals such as SIGINT... Background processes are  those  whose process  group  ID  differs  from  the terminal’s; such processes are immune to keyboard-generated signals." which is the same as the fixed ksh do.


Version-Release number of selected component (if applicable):
ksh-20120801-9.el6

Comment 3 errata-xmlrpc 2014-10-14 07:04:13 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.

http://rhn.redhat.com/errata/RHBA-2014-1381.html


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