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)
>>
>>> The second process is a zombie, which isn't killable until the parent tells
>>> it to go away. (Which could very possibly be the first kvt)
>>
>> Both still present empty terminal windows on my desktop and were spawned
>> from the KDE panel. The second one was running a copy of pine and was in
>> the same state as the other initially, until I kill -KILL'ed the pine
>> process, at which point it changed to what it is now.
>
> 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
Process 1103 is stopped (debug?). That's the T. It's also swapped
(W) and nice (N), which you can also see from the NI (nice) field.
Process 1109 is idle, swapped and a foreground process of a process
group.
Process 92724 is runnable, nice and running (no WCHAN). I really
don't understand why you can't stop this one.
Process 92743 is idle, swapped and a session leader.
> This seems to be more of a kvt bug than a freebsd bug. :)
I don't see that either. The fact that process 1103 is stopped is one
thing; is there a gdb process in sight?
Greg
--
See complete headers for address, home page and phone numbers
finger [EMAIL PROTECTED] for PGP public key
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
