autofs starts auto.local but not in auto.master
Hi there, Having another redhat to SuSE growing pain. 8) typically we'll put an entry into auto.master similar to: /n yp auto.local I've done this on the SuSE machines in the lab and we are seeing 'odd' behavior. after starting autofs via the init script, two atomounters are running: /usr/sbin/automount /n yp yp:auto.local /usr/sbin/automount /n yp auto.local If we remove nis from automount in nsswitch.conf, restart the kit we see automounter running (one instance) as expected. we are set. /usr/sbin/automount /n yp auto.local the question: running without an auto.master "n" directive (we would like this), it picks up "yp:auto.local" as the NIS map name, which doesn't exist. Its putting a "yp:" in the map name. Why is it the SuSE boxes are picking up yp:auto.local as the NIS map and most of our other boxes seem to be fine with things as is? (irix, rh, deb). thanks and have a great day! greg
Greg Whynott wrote:
typically we'll put an entry into auto.master similar to:
/n yp auto.local
I've done this on the SuSE machines in the lab and we are seeing 'odd' behavior.
Unless there are massive changes to the autofs scripts between 9.0 and whatever version you're running, you need to take a look at all the manpages for the automounter. This line in auto.master tells autofs to create an automount with mountpoint /n using mapfile yp, with option auto.local applied to each entry in that mapfile. See man auto.master; it is just a coincidence that this line yields a valid commandline for automount. In particular, there is no "n directive" for auto.master.
after starting autofs via the init script, two atomounters are running:
/usr/sbin/automount /n yp yp:auto.local /usr/sbin/automount /n yp auto.local
The second of these is started as per above. Everything in auto.local will be mounted under /n with a map-type yp (ie. a NIS database). I am not yet sure just why or how the first one is started. It is certainly unclear where that yp:auto.local is coming from. The autofs startup script isn't very easy to follow. What is the result of running: ypcat -k auto.master 2> /dev/null I can tell you that the autofs script should not start up that first automount instance unless this command has a non-null return.
participants (2)
-
Darryl Gregorash
-
Greg Whynott