Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 743302 - ksh script never comes back
ksh script never comes back
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: ksh (Show other bugs)
5.8
Unspecified Unspecified
medium Severity unspecified
: rc
: 5.8
Assigned To: Michal Hlavinka
qe-baseos-tools
:
Depends On: 742244
Blocks:
  Show dependency tree / graph
 
Reported: 2011-10-04 10:38 EDT by Michal Hlavinka
Modified: 2012-08-10 08:47 EDT (History)
5 users (show)

See Also:
Fixed In Version: ksh-20100621-2.el5
Doc Type: Bug Fix
Doc Text:
Previously, when using ksh, ksh became unresponsive when pipes were used in an "eval" argument. With this update an upstream patch has been applied and the ksh no longer hangs in the scenario described.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-02-21 00:51:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0159 normal SHIPPED_LIVE ksh bug fix and enhancement update 2012-02-20 09:53:47 EST

  None (edit)
Comment 3 Michal Hlavinka 2012-01-18 10:29:10 EST 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, when using ksh, ksh became unresponsive when pipes were used in an "eval" argument. With this update an upstream patch has been applied and the ksh no longer hangs in the scenario described.
Comment 4 errata-xmlrpc 2012-02-21 00:51:20 EST 
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-2012-0159.html
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.