Bug 245641

Summary: [RHEL5 Doc]: Certain bash commands have differing behavior when run as "sh" vs. "bash"
Product: Red Hat Enterprise Linux 5 Reporter: Chris Lalancette <clalance>
Component: bashAssignee: Tomas Janousek <tjanouse>
Status: CLOSED ERRATA QA Contact: Chris Ward <cward>
Severity: low Docs Contact:
Priority: low    
Version: 5.0CC: tao
Target Milestone: ---Keywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2008-0380 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-21 15:36:02 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:    
Bug Blocks: 246258    
Attachments:
Description Flags
Example bash man page update none

Description Chris Lalancette 2007-06-25 20:27:05 UTC 
Description of problem:
The behavior of certain builtin bash commands (including eval, exec, set, unset,
export, readonly, source, and trap) differ when operating either in "sh" mode,
or "posix" mode (I think they are the same thing, but I'm not 100% sure).  This
is a request to document those differences; for example, if in "sh" mode,
"export" with an invalid option will abort the script instead of continuing on.
 I will upload a preliminary version of the documentation from the customer; it
doesn't document the differences in any real detail, but might be a starting point.
Comment 1 Chris Lalancette 2007-06-25 20:28:14 UTC 
Created attachment 157808 [details]
Example bash man page update
Comment 2 RHEL Program Management 2007-10-16 03:56:30 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 8 errata-xmlrpc 2008-05-21 15:36:02 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2008-0380.html