From owner-freebsd-current Mon Sep 21 08:09:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24668 for freebsd-current-outgoing; Mon, 21 Sep 1998 08:09:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24627 for ; Mon, 21 Sep 1998 08:08:56 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id LAA22906 for ; Mon, 21 Sep 1998 11:08:19 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA21429; Mon, 21 Sep 1998 11:08:19 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.8.8/8.8.8) id LAA07483 for freebsd-current@freebsd.org; Mon, 21 Sep 1998 11:08:19 -0400 (EDT) (envelope-from jwd) From: John DeBoskey Message-Id: <199809211508.LAA07483@bb01f39.unx.sas.com> Subject: Hung amd on -current? To: freebsd-current@FreeBSD.ORG Date: Mon, 21 Sep 1998 11:08:19 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have the following 'amd' process on a current system which I cannot kill. 6969 root -18 0 940K 524K vmopar 0:00 0.00% 0.00% amd The parent amd process is still alive and working... Basically, all traffic to a machine 'nfssrv05' is now hung, which I believe is due to the above process.. Any ideas? Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message