Bug 1011576
Summary: | ksh, command substitution no longer works after a pipe | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | sorin <sserban> |
Component: | ksh | Assignee: | Michal Hlavinka <mhlavink> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.4 | CC: | brwillia, ken_nishimura, nobody, ovasik, redhat, sauchter |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-02-18 09:52:31 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
sorin
2013-09-24 14:56:25 UTC
reproducible in 6.4.z works in rhel-6.5 update to be At Agilent we're being bitten by this bigtime since we updated to RHEL 5.10 over Xmas. Numerous scripts are failing in ways that take hours to track down; one sysad script wrote junk in / on 40 systems. Can we up the severity? This seems to be related to the kernel. Both ksh version 20100621-18.el5 and 20100621-12.el5 fail under 2.6.18-371.1.2.el5 and newer, while they work under 2.6.18-348.6.1.el5. (Note, I did not check kernels between 348.6.1 and 371.1.2). What changed? Beware this bug is for RHEL6. For RHEL5, there is different bug #1028504 Yes, we are using RHEL5. But I get You are not authorized to access bug #1028504. I know. Some bugs are private because they can contain sensitive information. If you are Red Hat customer, you should use proper support channel (https://access.redhat.com/home). Support team will monitor the bug for you and forward important information. This bug should be closed. The issue should be fixed in RHEL-6.5 ksh. If someone can reproduce this issue with ksh >= 20120801-10.el6, let me know. Otherwise I will close this bug in a few days. |