From zanfur@u.washington.edu Fri May 18 16:26:02 2001 Received: from jason02.u.washington.edu (root@jason02.u.washington.edu [140.142.8.52]) by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4INPx018112 for ; Fri, 18 May 2001 16:25:59 -0700 Received: from dante16.u.washington.edu (zanfur@dante16.u.washington.edu [140.142.15.85]) by jason02.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4INPw030020 for ; Fri, 18 May 2001 16:25:58 -0700 Received: from localhost (zanfur@localhost) by dante16.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4INPwU77816 for ; Fri, 18 May 2001 16:25:58 -0700 Date: Fri, 18 May 2001 16:25:57 -0700 (PDT) From: "'Robin' R. Battey" To: UW Linux Group Subject: Re: locked directory? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Here's the official info: If an nfs mount is mounted soft, then the processes get automatically killed after a timeout period. If it's hard,nointr (default), then it waits forever and signals don't do anything (none of them do anything--not KILL, not QUIT, not anything). If it's mounted hard,intr (the recommended way), then you can kill a process with whatever signal would normally kill it (and -9 always works). Cheers! -robin -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ " R o b i n " R . B a t t e y PGP Key -- http://www.cs.washington.edu/homes/zanfur/pgpkey.pub 25B1 1CA6 590D 655C 2F91 73F8 1099 BFE6 09A0 0BD6 On Fri, 18 May 2001, William Kreuter wrote: > Earlier this year I regularly got nfs hangups. I couldn't kill with -9 if > it was a hard mount, but kill -9 on a soft mount worked fine. > > William Kreuter, Senior Computer Specialist, University of Washington > Ctr. for Cost & Outcomes Research, 146 N. Canal St. #300, Seattle, WA 98103 > billyk@u.washington.edu http://staff.washington.edu/billyk/ > voice or voice mail: 206-543-5007 fax: 206-543-5318 mailstop: 358853 > > .