home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.protocols.nfs:3223 comp.sys.sun.admin:10809
- Newsgroups: comp.protocols.nfs,comp.sys.sun.admin
- Path: sparky!uunet!ferkel.ucsb.edu!taco!gatech!swrinde!zaphod.mps.ohio-state.edu!howland.reston.ans.net!usc!news.service.uci.edu!ucivax!cwi!bob
- From: bob@cwi.com (Bob Parker )
- Subject: NFS automounter problems
- Message-ID: <C1HDC1.6Ex@cwi.com>
- Organization: CaseWare Inc.
- Date: Tue, 26 Jan 1993 21:36:00 GMT
- Lines: 33
-
- I posted this before, and got no response, but we were having problems
- with our news system, so I'll try again in case it never went out...
-
-
- Does anyone have an elegent solution to coexisting with the automounter?
-
- We have a software product that does 'pwd' and getwd() and uses
- that path for various things, sometimes the path is even passed to
- programs on other machines. This is fine if both machines have the path
- NFS mounted normally, but the automounter really throws a monkey wrench
- into things.
-
- Since the path returned by getwd() is the 'real' path, you get /tmp_mnt/...
- for automounted directories. Since we use the getwd() path, we don't access
- the files thru the automounter mapped pathnames, so the automounter is not
- aware that we are accessing files under it's control. Since the automounter
- unmounts the files after a period of inactivity, the path that worked fine
- becomes invalid, possibly at very inopportune times.
-
- It seems like we need something like getwd() but that gives us the path
- that is controlled by the automounter (so the automounter knows that the
- files are being accessed), rather than the 'real' path.
- Is there such a beast?
-
- Any other ideas?
-
- Thanks in advance for any help.
-
- --
- =======================================================
- || Bob Parker || ||
- || CaseWare, Inc || The floggings will continue ||
- || bob@cwi.com || until morale improves! ||
-