HP3000-L Archives

July 2001, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Lane Rollins <[log in to unmask]>
Reply To:
Lane Rollins <[log in to unmask]>
Date:
Tue, 31 Jul 2001 09:38:28 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
On the off chance was the session running an exegsys application from a
hardwired (dtc) terminal? If so they have a patch that at least under 6.0
made this problem go away. I really got tired of rebooting the system to
clear terminals.

If you do a showproc on the process shown by glance and it can't find a
process or it is related to a completely different session/application, then
it's time for a reboot.

-Lane

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
Behalf Of Steve Belkacem
Sent: Tuesday, July 31, 2001 9:31 AM
To: [log in to unmask]
Subject: Re: Session will not abort.


There is not CPU stavation which is causing this. The
session has been in this state since last Friday
night.

For most of this time(over the weekend, at night) the
system has been dormant.

This is how it is shown in glance. If you attempt to
KILL any processes within the session, the system says
that these are no longer active.

Steve

S9999 252 xxxxx,xxxxx.xxxx 543 MAIN       C188  0.0%
0.0   0   0.0  CPU

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2