Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: pickles@mpr.ca (Clive Pickles)
Newsgroups: comp.sys.sun
Subject: Re: How do I kill this?
Keywords: Miscellaneous
Message-ID: <2308@brchh104.bnr.ca>
Date: 2 Apr 91 15:00:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 28
Approved: Sun-Spots@rice.edu
X-Original-Date: Mon, 1 Apr 91 02:12:45 GMT
X-Refs:  Original: v10n65, Replies: v10n69
X-Sun-Spots-Digest: Volume 10, Issue 75, message 4
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

In article <2226@brchh104.bnr.ca> mike@sharebase.com (Mike Ubell) writes:
>In article <2150@brchh104.bnr.ca> you write:
>
>>How do I kill this process?
>>
>>root      6585  0.0  0.0   48    0 je S    15:47   0:00 <exiting>
>
>Reboot!

NOT NECESSARY!

>This looks like a flow control problem where the port frezes waiting
>for the output to drain but it has recieved an x-off (or cts has dropped,
>if enabled).  There is a patch: 100194-02 that seems to fix this.
***deleted stuff here
>If you want to try to free the port without rebooting you can connect a
>terminal with a null modem at the proper baud rate (if you know what it
>is) and type a CNTR-Q (or assert the cts line, as apropriate).

An EASIER way of doing this is to make yourself root, then put a trace on
this process.  On my 4.0.3 system, this "wakes the process up" and causes
it to finish exiting  (and also cleans up any defunct processes it may
have spawned).  The process should exit almost immediately.

But I agree with Mike...you should really get the patch.

= Clive Pickles - Systems Administrator MPR Teltech Ltd. (Ottawa) =
= Phone: (613) 787-4159 ------------------ E-mail: pickles@mpr.ca =