RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ This bug was initially created as a clone of Bug #659459 +++

Created attachment 464363 [details]
Reproduction script

Description of problem:

When creating a file inside a ksh script and then immediately attempting to open the new file the file does not exist.  This occurs even when the file creation is inside parentheses and the access occurs outside the parentheses and the filesystem is on a local disk.

Version-Release number of selected component (if applicable):

Client is reporting against 20100202-1.el5 (RHEL5) but I have also reproduced on 20100202-1.el5_5.1 (RHEL5).  This is also reproducable on 20100621-1.fc13 (Fedora 13) but seems to require more iterations.

How reproducible:

Attached are two files.  The first, ksh.bug, is a script which will reproduce the error.  The second, ksh.strace.out, is an strace of a failed run.  Search for "###" in the strace to find annotations displaying the failure

Steps to Reproduce:
1. Run ksh.bug

  
Actual results:
It seems that commands are being evaluated in an incorrect order.


Expected results:
As I understand it, the commands inside the parentheses should always be completed before the following commands are executed.

Created attachment 471863 [details]
patch to fix this

    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:
When a ksh script created a file and immediately opened it after the creation, the operation failed. This happened because the created file, in some cases, did not exist yet. With this update, this race condition has been fixed and once a file is created, it is immediately available for any following commands.

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 therefore 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-2011-0645.html