On Fri, 2006-10-27 at 16:22 -0400, David Meleedy wrote: > Are there any plans to implement this correctly? We are seeing > problems with the auto.net script that just loads up every > directory provided by the machine. For example some of our > fileservers have a lot of mounts, and this can really start > filling up the mount table. Also, some fileservers let certain > clients mount some of the directories provided but not others. > The error messages are confusing our user's because they are > trying to cd to: > > /net/<machine_name>/foo > and they see an error message about not being able to mount > /net/<machine_name>/goo > > It would be a lot cleaner if only the directory you are cd'ing > to got mounted instead of every directory.
As Jeff says, autofs version 5 works in a similar way to other automounters now, by mounting (and expiring) the exported shares as you go. There is also a built in "-hosts" map now. However, I've recently discovered that I haven't covered some of the export access control syntax used by Solaris servers so you may still need to use the auto.net script. This issue will never be fixed in version 4 because version 4 cannot handle the nesting of mounts found in server export lists. Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
