Red Hat Bugzilla – Bug 244117
service autofs start when the service is running does not return success
Last modified: 2009-10-06 03:11:19 EDT
Description of problem:
See the LSB standard for init script behaviour. If /etc/init.d/autofs start is
issued, and the service is already running, the init script should return
success. This is another regression from version 4.
Version-Release number of selected component (if applicable):
Sorry, didn't have time to get this into RHEL-5.2.
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
(In reply to comment #0)
> Description of problem:
> See the LSB standard for init script behaviour. If /etc/init.d/autofs start is
> issued, and the service is already running, the init script should return
> success. This is another regression from version 4.
A quick check shows that the init script now returns success
when automount(8) is already running but this is more by
chance that design.
Looking at this I see we're not returning the status to the
parent when automount(8) is waiting for the daemon to finish
I'll fix this.
This issue has been fixed in the latest autofs package
Release note added. If any revisions are required, please set the
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.
* previously, automount did not return its status to its parent while it waited for the autofs daemon to complete its startup. As a result, the init script did not always report success when the service started sucessfully. Automount now returns its status and accurately reports when the service has started.
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.