Jeff Moyer wrote: > > gml4410> For -null, it just adds the mountpoint location to the list of > gml4410> knownmaps, but doesn't do anything else. > > This isn't exactly right. It should "nullify" the next occurrence of the > given mount point, and then go away. That isn't how automount maps are supposed to work (at least not Sun ones, according to how I read the documentation). Only the *first* occurrence of a mountpoint is supposed to be used - that is meant to override *all* following occurences.
> Consider a map like this: > > /home -null > +auto.master > /home /etc/auto.home > > Let's assume that +auto.master reads the master map from nis, and the nis > master map defines /home to point to some nis map. The above would ignore > the /home entry in the nis master, and allow us to replace it with our own. If you want to replace an entry in NIS you add your entry *before* loading the NIS maps. So to set your own /home to override the NIS one you use: /home /etc/auto.home +auto.master The -null map is so that you may wipeout *all* occurrences of a mountpoint that you would otherwise have. At least that's how I've always read it. In that respect it is no different to something like: /amp auto.map1 /amp auto.map2 /amp auto.map3 where I would expect to see auto.map1 used on /amp, since once there is a map on a mountpount it won't be overridden. Also note - we're talking about Sun-style automounts here. Anyone with OSF1 would (might) know they do everything backwards (the *last* map wins...) _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
