Bug 527375

Summary: Read and write size of startup status report buffer is incorrect
Product: Red Hat Enterprise Linux 4 Reporter: Ian Kent <ikent>
Component: autofs5Assignee: Ian Kent <ikent>
Status: CLOSED ERRATA QA Contact: yanfu,wang <yanwang>
Severity: medium Docs Contact:
Priority: low    
Version: 4.8CC: fnadge, ikent, jmoyer, yanwang
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: autofs5-5.0.1-0.rc2.110 Doc Type: Bug Fix
Doc Text:
Previously, autofs the calculated pipe read size incorrectly. As a result, the init script did not always report success even when the service started successfully. Now, the buffer size is calculated correctly.
Story Points: ---
Clone Of: 487656 Environment:
Last Closed: 2011-02-16 14:21:23 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: 487656    
Bug Blocks:    

Comment 2 yanfu,wang 2010-12-21 03:31:05 UTC
verified autofs-5.0.1-start-pipe-buff-size.patch applies cleanly during the build, and there are a lot of RHTS tests that start and stop autofs often
and almost always check the return status, no regression found as per the regression results.

Comment 3 Florian Nadge 2011-01-03 16:27:40 UTC
    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, autofs the calculated pipe read size incorrectly. As a result, the init script did not always report success even when the service started successfully. Now, the buffer size is calculated correctly.

Comment 4 errata-xmlrpc 2011-02-16 14:21:23 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 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-0241.html