From owner-freebsd-questions Wed Jun 17 20:13:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03596 for freebsd-questions-outgoing; Wed, 17 Jun 1998 20:13:33 -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 UAA03585 for ; Wed, 17 Jun 1998 20:13:28 -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 XAA00935; Wed, 17 Jun 1998 23:13:16 -0400 (EDT) Date: Wed, 17 Jun 1998 23:13:16 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: Keith Jones cc: questions@FreeBSD.ORG Subject: Re: Killing a process? In-Reply-To: <19980617205355.07464@blueberry.co.uk> 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 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... Charles Charles Sprickman spork@super-g.com ---- On Wed, 17 Jun 1998, Keith Jones wrote: > On Wed, Jun 17, 1998 at 07:49:23PM +0100, Keith Jones wrote: > > > > > Actually Dan's right. If you can free up whatever resource is causing the > process to become 'stuck' this is a far better option.... > > Keith > -- > v Keith Jones Systems Manager, Blueberry New Media Ltd. v > | Postal Mail: 2/10 Harbour Yard, Chelsea Harbour, LONDON, UK. SW10 0XD | > | Telephone: +44 (0)171 351 3313 Fax: +44 (0)171 351 2476 | > ^ Email: Keith.Jones@blueberry.co.uk WWW: http://www.blueberry.co.uk/ ^ > > 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