home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!cgl!cgl.ucsf.edu!srp
- From: srp@cgl.ucsf.edu (Scott R. Presnell)
- Newsgroups: comp.sys.sgi
- Subject: Re: automount mounts on ls
- Message-ID: <srp.722377368@cgl.ucsf.edu>
- Date: 21 Nov 92 20:22:48 GMT
- References: <orman.722110315@pv0238.vincent.iastate.edu>
- Sender: news@cgl.ucsf.edu (USENET News System)
- Organization: UCSF Computer Graphics Lab
- Lines: 38
-
- orman@iastate.edu (David L Orman) writes:
-
- >Automount mounts everything in a directory when you do an ls in the
- >mount points directory, that is really annoying is there some way around
- >it?
-
- >ex:
- > I mount indy:/usr/indy on /usr/indy on animate and when I do an ls in
- >/usr it mounts it, which means I have to wait for them all to mount. We
- >mount about 14 machines so this takes a while.
-
- >Any suggestions?
-
- It sounds like you're using a direct mount - if you want to see the
- attributes of the remote /usr/indy, then yes the automounter mounts it.
-
- The other choice is to use an indirect mount. If you indirectly mount
- indy:/usr/indy under /home on animate (or some such), you'll not trigger a
- mount by looking in /home, of course you'll not see anything under /home.
- You'll have to know that the automounter is waiting on /home, for a
- reference down into /home/indy. If you're doing mounts for home
- directories - use an indirect mount.
-
- In the situation you've described 14 direct mounts - you've just generated
- 28 or more RPC calls plus the 14 NFS getattr() calls for ls in less than a
- second. Can you say "mount storm?" I *knew* you could.
-
- (It would be more efficent to simply leave the remote fs's statically
- mounted.)
-
- If you have not already, I would stronly suggest reading the NFS/NIS
- Administration guide - especially those sections dealing with automounting.
-
- - Scott
-
- --
-
- - Scott Presnell (srp@cgl.ucsf.edu)
-