Bug 1367309
Summary: | grep -r has been broken in RHEL 6.7 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Marcel Kolaja <mkolaja> |
Component: | grep | Assignee: | Ondřej Lysoněk <olysonek> |
Status: | CLOSED ERRATA | QA Contact: | Jan Kepler <jkejda> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 6.7 | CC: | cww, fkrska, isenfeld, jdeenada, jkejda, jskarvad, mkolaja, olysonek, ovasik, pdwyer, salmy, sivathanut |
Target Milestone: | rc | Keywords: | Patch, Regression, ZStream |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | grep-2.20-5.el6_8 | Doc Type: | Bug Fix |
Doc Text: |
Cause:
Grep update fixed old bug regarding '-r' switch which may lead to incompatibility with some old badly written scripts.
Consequence:
Previously 'grep -r PATTERN' wrongly read STDIN. After the grep update 'grep -r PATTERN' recursively scans current directory for files containing the PATTERN which is according to its documentation. This behavior may break some old badly written scripts.
Fix:
Backward compatibility environment variable GREP_LEGACY_R has been introduced, which if set to '1', causes grep to behave the old buggy way, otherwise the grep behaves the new way.
Result:
Now, if GREP_LEGACY_R environment variable is set to '1', 'grep -r PATTERN' reads STDIN, otherwise it recursively scans current directory for files containing the PATTERN.
|
Story Points: | --- |
Clone Of: | 1256756 | Environment: | |
Last Closed: | 2016-10-04 21:59:39 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1256756 | ||
Bug Blocks: |
Description
Marcel Kolaja
2016-08-16 07:48:52 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. https://rhn.redhat.com/errata/RHBA-2016-2000.html |