Path: utzoo!yunexus!torsqnt!dptcdc!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: enme1!caveh@uunet.uu.net (Caveh Jalali)
Newsgroups: comp.sys.sun
Subject: how to KILL <exiting> process
Keywords: SunOS
Message-ID: <812@cs-spool.calgary.UUCP>
Date: 8 Mar 89 16:45:46 GMT
Article-I.D.: cs-spool.812
References: <8902160057.AA07420@wubios.WUstl.EDU>
Sender: usenet@rice.edu
Organization: U. of Calgary, Calgary, Alberta, Canada
Lines: 20
Approved: Sun-Spots@rice.edu
Original-Date: Tue, 28 Feb 89 15:24:34 EST
X-Sun-Spots-Digest: Volume 7, Issue 187, message 10 of 15
X-Issue-Reference: v7n165

In article <8902160057.AA07420@wubios.WUstl.EDU> david@wubios.wustl.edu (David J. Camp) writes:
>...Frequently when a modem login session terminates by an
>unclean method, the modem is no longer available for login....
>There is a process left that owns the modem, which
>says <exiting> as the command.  This process cannot be killed by the super
>user.  To solve this we have been rebooting.  Is there a better solution?

Since no one has proposed a better solution than to reboot the system,
I'll offer my $0.02's worth.

Good news:  There is a "nice" way to kill such processes!

As root do: "trace -p <PID>", where <PID> is the hung process.  Then, hit
^C to detach the trace.

PROCESS DEAD!!!

We are running SunOS 4.0.1 on 3/280's.

	-cj