Bug 5796 - autofs start script ignores NIS maps
autofs start script ignores NIS maps
Status: CLOSED DUPLICATE of bug 6484
Product: Red Hat Linux
Classification: Retired
Component: autofs (Show other bugs)
6.1
All Linux
high Severity high
: ---
: ---
Assigned To: Cristian Gafton
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-10-10 01:28 EDT by chauvin
Modified: 2008-05-01 11:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-11-01 17:35:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description chauvin 1999-10-10 01:28:19 EDT
A logic error in /etc/rc.d/init.d/autofs prevents automount
from being started for maps that are received through NIS.

the function 'getmounts()' in the autofs start script does
the following:

    if[ -f /etc/auto.master ] then
         start automount for mount points in/etc/auto.master
    else
         search for mount points in NIS maps.
    fi

this logic prevents maps from being loaded from _both_
/etc/auto.master and over NIS.  The fix for this is quite
simple: test first for /etc/auto.master and then test for
NIS maps.  I'd be happy to provide a patch if this
explanation isn't clear.

thanks!


------- Additional Comments From   10/14/99 06:01 -------
A quick fix is to use the startup script from 6.0
Although not the best of solutions, I need my system up and running.


------- Additional Comments From   10/20/99 13:44 -------
Autofs should check /etc/nsswitch.conf to determine if it should use
NIS at all.  In 6.0, you could say "automount: files" in
/etc/nsswitch.conf, and autofs it would still check NIS.  It looks
like this change in 6.1 was meant to remedy the problem, but the best
solution was not chosen.
Comment 1 Bill Nottingham 1999-11-01 17:35:59 EST
*** This bug has been marked as a duplicate of 6484 ***

Note You need to log in before you can comment on or make changes to this bug.