Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!crdgw1!uunet!rayssd!sud509!heiser@tdw201.ed.ray.com
From: heiser@tdw201.ed.ray.com
Newsgroups: comp.sys.apollo
Subject: Re: NFS Mount Point Strategy?
Message-ID: <3437@sud509.ed.ray.com>
Date: 30 Nov 90 17:05:37 GMT
References: <1990Nov10.144551.809@alchemy.chem.utoronto.ca> <3737@skye.ed.ac.uk> <1042@inews.intel.com>
Sender: heiser@sud509.ed.ray.com (Bill Heiser - Unix Sys Admin @ Raytheon Company, Sudbury MA)
Organization: Raytheon Company, Sudbury MA
Lines: 25

In article <1042@inews.intel.com> kseshadr@quasar.intel.com (Kishore Seshadri) writes:
>In article <3737@skye.ed.ac.uk>, richard@aiai (Richard Tobin) writes:
>>In article <1990Nov10.144551.809@alchemy.chem.utoronto.ca> system@alchemy.chem.utoronto.ca (System Admin (Mike Peterson)) writes:
>>>2) What directory structure is best for the actual mount points:
>>
>>We mount system:dir on /nfs/system/dir and have a symbolic link to this.
>>This has the advantage that when getwd() searches a directory, it never
>>looks at unnecessary remote mount points.
>>
>This does not necessarily fix the hanging problem for SunOS 4.0.x systems.
>The getwd() algorithm was changed to where, every time a mount point is
>crossed, getwd checks the /etc/mtab and tries to find a mount moint with

Does this mean that there is not a way to stop the "hanging problem" 
in SunOS 4.0.x systems?  In this environment, does the /nfs/system/dir
mount point strategy have any advantage over /mountpoint strategy?

Thanks in advance ...


-- 
Work:	heiser@tdw201.ed.ray.com
	{decuac,necntc,uunet}!rayssd!tdw201.ed.ray.com!heiser
Home:	bill@unixland.uucp		| Public Access Unix  508-655-3848
	uunet!world!unixland!bill	| 1200/2400/9600/19200 PEP/V32/V42