From owner-freebsd-bugs Thu Jan 17 6:30:10 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A7BDD37B400 for ; Thu, 17 Jan 2002 06:30:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0HEU2W64712; Thu, 17 Jan 2002 06:30:02 -0800 (PST) (envelope-from gnats) Date: Thu, 17 Jan 2002 06:30:02 -0800 (PST) Message-Id: <200201171430.g0HEU2W64712@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: David Malone Subject: Re: kern/33978: can't kill process Reply-To: David Malone Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/33978; it has been noted by GNATS. From: David Malone To: Gerard Kok Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/33978: can't kill process Date: Thu, 17 Jan 2002 14:21:43 +0000 On Thu, Jan 17, 2002 at 01:04:05AM -0800, Gerard Kok wrote: > Sometimes one of the child-processes of cups enters some sort of > endless loop, and there is no way to kill it, not even with kill -9. > This is extremely awkward, since this process keeps the printerport > open, so effectively printing is down. Can you have a look at the process with top and tell us what state the process is in? Thanks, David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message