Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: mike@sharebase.com (Mike Ubell)
Newsgroups: comp.sys.sun
Subject: Re: How do I kill this?
Keywords: Miscellaneous
Message-ID: <2226@brchh104.bnr.ca>
Date: 27 Mar 91 21:35:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 19
Approved: Sun-Spots@rice.edu
X-Original-Date: Wed, 27 Mar 91 08:35:40 PST
X-Refs:  Original: v01n65
X-Sun-Spots-Digest: Volume 10, Issue 69, message 16
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

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!

This looks like a flow of 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.
Unfortunately it seems to have the side effect that the local designation
in /etc/ttytype does not work on the higher numbered alm ports.  If this
was a tip it could be the cts problem in which case you cna change your
remote entry to remove the "hf" designation, if present.

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).