HP3000-L Archives

February 1996, 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:
Nick Demos <[log in to unmask]>
Reply To:
Nick Demos <[log in to unmask]>
Date:
Wed, 28 Feb 1996 15:29:25 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
----------
From:   Jerry Fochtman[SMTP:[log in to unmask]]
Sent:   Tuesday, February 27, 1996 3:47 PM
To:     Multiple recipients of list HP3000-L
Subject:        Re: Re[2]: Capturing Console Log Records as they are written
 
At 01:38 PM 2/27/96 -0400, Chris Bartram wrote:
> In <[log in to unmask]> [log in to unmask] =
writes:
>
>> About 10 minutes before I left the office tonight I got a rather =
strange
>> request.  Apparently there is some need (I guess I'll be enlightened =
later)
>> for capturing console log records as they are written.
>>
 
>
>Seems to me if you want to do anything with console messages, you're =
easiest
>and cheapest bet is probably a piece of hardware like Telamon's console =
engine
>or something.
 
How "real time' do you need them?  It's been a long time, but I recall =
we had a similar requirement.
We wrote a program that stayed up all the time.  It checked the current =
log file every X seconds and kept track of what it had processed, by =
time and/or record number, I forget which, but our problem was how to =
only capture the ones after any particular startup if the system failed
 
Hope this helps. =20
 
Nick

ATOM RSS1 RSS2