home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!wupost!gumby!yale!yale.edu!think.com!barmar
- From: barmar@think.com (Barry Margolin)
- Newsgroups: comp.sys.sun.admin
- Subject: Re: automounter vs auto.master
- Date: 2 Sep 1992 19:13:41 GMT
- Organization: Thinking Machines Corporation, Cambridge MA, USA
- Lines: 16
- Message-ID: <1833p5INN93m@early-bird.think.com>
- References: <1811ojINNe3c@cs.utexas.edu> <rhoward.715453276@matd>
- NNTP-Posting-Host: telecaster.think.com
-
- In article <rhoward.715453276@matd> rhoward@matd.gatech.edu (Robert L. Howard) writes:
- > Entries in both direct and indirect maps can be modified at
- > any time. The new information will be used when automount
- > next uses the map entry to do a mount. automount does not
- > cache map entries.
-
- That will work for changing existing direct map entries and for adding
- entries to indirect maps, but it won't let you add or delete direct map
- entries or new indirect maps. The automounter only creates the (pidNNN)
- mounts, which implement direct mounts and indirect maps, when it first
- starts up.
- --
- Barry Margolin
- System Manager, Thinking Machines Corp.
-
- barmar@think.com {uunet,harvard}!think!barmar
-