From owner-freebsd-current  Sat Jul 24 23:22:19 1999
Delivered-To: freebsd-current@freebsd.org
Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6])
	by hub.freebsd.org (Postfix) with ESMTP id B934B15081
	for <current@FreeBSD.ORG>; Sat, 24 Jul 1999 23:22:14 -0700 (PDT)
	(envelope-from toasty@celery.dragondata.com)
Received: (from toasty@localhost)
	by celery.dragondata.com (8.9.3/8.9.3) id BAA55777;
	Sun, 25 Jul 1999 01:21:03 -0500 (CDT)
	(envelope-from toasty)
From: Kevin Day <toasty@dragondata.com>
Message-Id: <199907250621.BAA55777@celery.dragondata.com>
Subject: Re: Unkillable processes
In-Reply-To: <19990725154108.A51019@freebie.lemis.com> from Greg Lehey at "Jul 25, 1999 03:41:09 pm"
To: grog@lemis.com (Greg Lehey)
Date: Sun, 25 Jul 1999 01:21:03 -0500 (CDT)
Cc: toasty@dragondata.com (Kevin Day), kkenn@rebel.net.au,
	current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (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

> On Saturday, 24 July 1999 at 20:51:37 -0500, Kevin Day wrote:
> >> On Sat, 24 Jul 1999, Kevin Day wrote:
> >>
> >>> For one, do another 'ps' with the 'l' option, so you can see what it's stuck
> >>> on.
> >>
> >>   UID   PID  PPID CPU PRI NI   VSZ  RSS WCHAN  STAT  TT       TIME COMMAND
> >>  1000  1103  1086  29  75 20  5740  384 -      TWN   ??    0:00.00 (kvt)
> >>  1000  1109  1103   0   4  0  1504    0 ttywri IWs+  p1    0:00.00 (tcsh)
> >>
> >>  1000 92724  1086 279 105 20  5736  356 -      RN    ??  139:40.13 kvt -T Termi
> >>  1000 92743 92724   2  18  0  1576    0 pause  IWs   p8    0:00.00 (tcsh)
> >>
> > Well, since the CPU time in the active process (92724) went up since your
> > last e-mail, and it's in the RUN state (a - in the WCHAN and a R in the
> > STAT), it looks like the process is just spinning, eating CPU.
> 
> Right.
> 
> > The tcsh listed below that is a zombie of the running kvt. 
> 
> There aren't any zombies here.  
> 
> It's a child of the kvt.  It's not a zombie.  Take a look at the STAT
> field (and ps(1)): process 

Good point, i didn't notice that, i saw the ()'s from his first message,

> Process 92724 is runnable, nice and running (no WCHAN).  I really
> don't understand why you can't stop this one.

The only time I've seen this is when my console is getting flooded with
'vm_fault: pager error' messages for that process. Otherwise, there's no
reason why a running process can't be killed, correct?

Kevin


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message