Nalin Dahyabhai writes:
> On Mon, Jun 05, 2000 at 11:53:14AM -0700, Rich McClellan wrote:
> > The point made by Gooch, and an *extremely* good one because we want Linux
> > to behave like the other Unices out there, is that the file nsswitch.conf
> > should specify the behavior of map lookups, not some ad hoc check for a
> > file.
>
> 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.
/etc/nsswitch.conf is used to decide which *master* maps are
consulted. The master maps bring in other maps for each automount
mount point.
> 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,
Yes!
> 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.
The problem was that the silly script was testing for /etc/auto.master
existence, and if it existed, totally ignored the auto.master NIS map.
This was probably done in the name of "flexibilty", but it was the
wrong approach. Said flexibility belongs in /etc/nsswitch.conf.
Regards,
Richard....
Permanent: [EMAIL PROTECTED]
Current: [EMAIL PROTECTED]
