Description of problem: autofs doesn't start up when running "service autofs start" if the maps are empty. I understand that this is probably by design, but it leads to another bug. If you have autofs on in chkconfig, then change the map and call "service autofs reload", it should load the new map. However, because the service doesn't start when the map is empty, the reload (as well as the condrestart) both fail to make autofs turn on. When autofs is turned on in chkconfig, scripts and programs should have the expectation that autofs is running when the machine is on, and should be able to call condrestart and reload without worrying about it failing. Version-Release number of selected component (if applicable): autofs-4.1.3-169 How reproducible: Always Steps to Reproduce: 1. Autofs is off; user is root 2. Supply an empty /etc/auto.master file (the default file installed by the rpm is fine) 3. Run "/sbin/service autofs start" 4. Replace the auto.master file with one that has at least one mount 5. Call "/sbin/service autofs reload" or "/sbin/service autofs condrestart" Actual results: autofs fails to reload / restart. Expected results: autofs SHOULD reload / restart Additional info:
Created attachment 132695 [details] Patch for /etc/init.d/autofs This one-line patch fixes this bug. This init.d file is written, however, for both Debian and RedHat. My patch only addresses the issue on RedHat. I don't even know if the bug exists on Debian.
This is simple enough. Thanks!
Proposed for 4.5.
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.
A fix for this problem was committed to autofs-4.1.3-195. Alex, if I provide updated packages, would you be willing to confirm that they fix your problem?
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-2007-0274.html