rahmeh@cerc.utexas.edu (Joe Rahmeh) (03/15/91)
If the user home directory is on an NFS filesystem (mounted from a SUN) the the K shell will not work: - it hangs the console when the user logs in - it cannot be killed from another terminal - you have to hit the yellow button Is there a workaround? Thanks Joe Rahmeh (rahmeh@cerc.utexas.edu)
john@johnmad.austin.ibm.com (03/15/91)
>If the user home directory is on an NFS filesystem (mounted from a SUN) > - it hangs the console when the user logs in > - it cannot be killed from another terminal > - you have to hit the yellow button This is, unfortunatly a common problem. Probably you are not running statd and lockd on the SUN, or there is some config problem that is keeping network locks from working between them. The ksh attempts a lock on the history file, and since most users keep the hist file in /u somewhere, that is an over the wire lock request. If it cannot complete the request, then you get the hang. >Is there a workaround? Yep, IMHO the best one is to keep your history files local on the machine you are logging into. This not only avoids locking problems, but is a great performance enhancement. You not only avoid the network locking, but are not continually reading and writing the darn hist file over the network all day. Another fix is forthcoming from IBM, by turning off the hist file locking. The fix is in 3003 or there abouts. Statements made here are my personal views and do not reflect policy or commitments of IBM Corporation. John Maddalozzo IBM Advanced Workstation Division internet: john@wizards.austin.ibm.com IBM Advanced Workstation Division aesnet: john@johnmad.austin.ibm.com 11400 Burnet Road, 994/3401 vnet: JOHNMAD at AUSVMQ Austin, TX, 78758-3493 uucp: cs.utexas.edu:ibmaus!auschs!johnmad.austin.ibm.com!john
rudy@chukran.austin.ibm.com (03/15/91)
> If the user home directory is on an NFS filesystem (mounted from a SUN) > the the K shell will not work: > - it hangs the console when the user logs in > - it cannot be killed from another terminal > - you have to hit the yellow button Most likely cause is that the server is not running the NFS lock manager. For some strange reason, ksh tries to lock the history file. If the server lock manager is not running, the client hangs. ********************************************************************* Rudy Chukran | EMAIL: IBM AIX Porting Center | RSCS: CHUKRAN at AUSTIN 11400 Burnet Rd. | AWDnet: rudy@chukran.austin.ibm.com Internal ZIP 2830 | internet: chukran@austin.iinus1.ibm.com Austin, Texas 78758 | Voice: 512-838-4674 Tieline: 678-4674 *********************************************************************
scl@sasha.acc.Virginia.EDU (Steve Losen) (03/18/91)
There is a bug in the SunOS NFS file locking code. This is fixed in 4.1.1 and there is a patch for 4.1 (and perhaps 4.0.3). The patch includes a new lockd and some new .o files for the kernel, which you must rebuild. Call up Sun and ask about it. You can work around the bug by being sure your ksh process on a RS/6000 does not put its history file on a sun. By the way, this bug also prevents pcnfs from working. -- Steve Losen scl@virginia.edu University of Virginia Academic Computing Center