HP3000-L Archives

April 1998, 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:
John Burke <[log in to unmask]>
Reply To:
John Burke <[log in to unmask]>
Date:
Thu, 30 Apr 1998 07:22:10 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
Yes it is dangerous, though the level of danger depends on activity;
i.e. how many console messages are being generated over a given period
of time. The buffer is pretty generous now as compared with MPE V days
but when it fills up I believe the result is the same: any process that
generates a console message will hang. Like logons and logoffs.

A likely cause for the console to behave as if STOP were pressed?
Someone inadvertently hits the space bar starting a terminal read and
suspending the display of console messages.

John Burke
e-mail: [log in to unmask]


-----Original Message-----
From: Costas Anastassiades [mailto:[log in to unmask]]
Sent: Thursday, April 30, 1998 9:42 AM
To: [log in to unmask]
Subject: Console Messages


Just curious about a situation :
A remote console (dev 21) every now and then will stop displaying the
various operator messages. As if STOP was pressed. Haven't really looked
into why or when it does this, as a Return will "revive" the sleeping
console and start displaying all the waiting messages.
But is this dangerous ? is there any limit to the number of messages
waiting to be displayed or TELLOPed ? what would the consequences be if
that limit was ever reached ?

Thank you as always,

Costas Anastassiades,
Intracom SA
Athens-Greece

ATOM RSS1 RSS2