On Mon, 5 Jun 2000, Nalin Dahyabhai wrote:
>
> Okay, I'm probably just being very dense, but I'm having trouble figuring
> out how a single line in nsswitch.conf is going to work if you're using
> multiple mount directories.
>
> For example, say I've set up automounting on both /home and /mnt. The
> auto.master map looks like this:
>
> /mnt /etc/auto.mnt --timeout 60
> /home/devel yp:auto.home --timeout 60
>
> Unless you're just talking about deciding which auto.master map to look in
> first, I can't see how the automount: line in nsswitch.conf can be of any
> use here.
>
> And if you're looking at both (which I think we all agree is a good thing),
> the only place the order makes a difference is if the maps conflict, and
> the only good reason to set up a workstation this way is to make entries in
> the local file override the NIS map's entries ("files nis"). Otherwise,
> you wouldn't bother putting them in the local file in the first place.
>
> Nalin
>
Under Solaris, your auto_master map would be:
/mnt auto_mnt
/home/devel auto_home
and in /etc/nsswitch.conf you'd have:
automount: files nisplus
and you'd have an /etc/auto_mnt and an auto.home yp map.
A worked example is, we have a Solaris cluster of ~100 Suns with about
20 Linux clients. They can all pickup ~250 auto-mounted data disks from
each other but have a few small customized local /etc/ maps to pick up
local software mirrors, or other minor customisations (like rw on the
software servers vs ro for the clients).
Actually, most customisation is done through NIS+ subdomains but
that's a whole different discussion under Linux...
Pete.
