From owner-freebsd-questions Wed Jun 17 23:50:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29529 for freebsd-questions-outgoing; Wed, 17 Jun 1998 23:50:07 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29496 for ; Wed, 17 Jun 1998 23:50:03 -0700 (PDT) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id CAA21311; Thu, 18 Jun 1998 02:49:50 -0400 (EDT) Date: Thu, 18 Jun 1998 02:49:50 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: Dean Hollister cc: Keith Jones , questions@FreeBSD.ORG Subject: Re: Killing a process? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That's odd. I'm not sure what else can hold a process. How about posting a ps showing the process, the output of mount, and a df for good measure? Charles Charles Sprickman spork@super-g.com ---- On Thu, 18 Jun 1998, Dean Hollister wrote: > On Wed, 17 Jun 1998, spork wrote: > > > Sounds like an nfs mount has stopped responding, if the nfs server comes > > back, you should be able to kill it. NFS seems to be the number one > > culprit when you have a process in disk wait from my experience... > > Hmmm. But we're not using nfs... > > Regards, > > d. > > +-------------------------------------------------------+ > | Dean Hollister, | dean@mushka.ml.org | > | Perth, Western Australia. | 12840184 ICQ | > +-------------------------------------------------------+ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message