+++ This bug was initially created as a clone of Bug #199441 +++ 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: -- Additional comment from ayacoub on 2006-07-19 12:41 EST -- Created an attachment (id=132695) 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 bugzilla has Keywords: Regression. Since no regressions are allowed between releases, it is also being proposed as a blocker for this release. Please resolve ASAP.
This issue is resolved in autofs-5.0.1-0.rc2.64.
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-0354.html