Subject: | |
From: | [log in to unmask][log in to unmask], 24 Sep 1998 14:54:44 EDT527_US-ASCII Patrick Santucci writes: > To get only off-topic posts, including Wirt's Amazing Encyclopedic > Ruminations(tm), it should be possible to send: > > SUBSCRIBE HP3000-L DIGRESS > > (I know, I used that joke a couple days ago, but with all the off-topic > traffic lately I thought it was Wirt -- I mean worth -- repeating :) > > Patrick > > P.S. Wirt, you alluded to your Arabic being a little rusty. Just how > many languages do you know? [...]37_24Sep199814:54: [log in to unmask] |
Reply To: | |
Date: | Mon, 28 Sep 1998 08:51:55 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
I've recently experienced two incidents where a Telnet session has ended up
in a hung state, that is, after an abortjob, the session persisted and tied
up a database. Only after a reboot was I able to clear the session.
What causes a session to hang like this? Is there anything I can do to
prevent it? Or, what action could I take (besides a reboot) to clear the
session.
In attempting to clear it, I tried ABORTJOB, I stopped the INETD job, I
stopped Network services, I tried a PM program to KILL specified PIN's.
Nothing worked.
Any insight would be appreciated.
Mike Gabriel
Rockwell Collins
|
|
|