[comp.sys.next] A problem with NFS?

flur@eedsp.gatech.edu (Peter W. Flur) (10/05/89)

I have upgraded to 1.0 on two of our machines that are directly connected
via a thin cheapernet with Capped T-Connectors at either end.  Evenually,
if our building ever gets the campus trunk to the third floor, we will
tie into the campus heterogeneous network.  For now, it consists soley
of to NeXT machines.  

The two machines each have the proper setup configuration according to
our documentation (subnet, dynamic routing, etc).  Each machine has the
other's mounted via NFS.  All user's directories are on one machine or
the other, but not both.

This is what I see:  When I am on the machine which my filespace does
NOT physically reside, it takes an incredible amount of time (20-40
seconds) to execute commands in a Terminal window (i.e. ls, cd, df, etc.) 
The machine then hangs until the command completes execution.  Not only
is this annoying and dangerous, it's not fun.  These same symptoms appear
on both machines to users with filespace on the other.

Could this be a problem with NFS?  

Peter

P.S. While I'm on the subject, does it take a tremendous amount of
time (compared to 0.9) for the workspace to exit when logging out?

   ----------------------------Peter Flur----------------------------
			   USMAIL: Box 32500
   Georgia Tech, School of Electrical Engineering, Atlanta, GA  30332
    USENET: ...!{allegra,hplabs,ihnp4,ulysses}!gatech!clemson!flur
	INTERNET: flur@clemson.gatech.edu, gt2500a@prism.gatech.edu
	                 PHONE: (404) 894-2955