HP3000-L Archives

January 1995, Week 1

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:
Guy Smith <[log in to unmask]>
Reply To:
Guy Smith <[log in to unmask]>
Date:
Fri, 6 Jan 1995 10:40:43 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (60 lines)
This lengthy message concerns systems logging, so you might
want to skip it if such thing bore you.
 
A while back, I wrote a utility call CMSG (in the CSL) which
(a) perpetually scans the system log file for console
messages, (b) logs these to a circular file and (c) allows
anyone to browse this log file.  While writing this, and
investigating console logging systems, I had a few thoughts
(and these few blew my allotment for 1994).
 
[1] Does anyone like the notion of filtering console
messages?  I'd like the ability to limit what gets displayed
on the console, and alternately highlight some messages.
 
The purpose of filtering would be to reduce the clutter
operators have to deal with.  Highlighting would allow me to
make certain message stand-out, and alert operators to a
problem.
 
I envision HP providing a string matching facility that
would allow you to define ignore/highlight criteria.  The
configuration could be kept in a text file in PUB.SYS, and
read at system start-up, or perhaps re-read with a parameter
added to SWITCHLOG.
 
Since the volume of displayed console messages is low, this
should create much overhead.
 
BTW, I know about OpenView Operations Center and other tools
that do console monitoring/logging, but cannot justify that
expense.
 
[2] Anyone know of a simple way to intercept console
messages?  CMSG must rip-and-read the system log files.  A
problem with this is that CMSG cannot read the most current
messages since they are in the last block of the variable
length system log file.  That makes CMSG less-than-real-
time, and less than completely useful.
 
I've looked into PE AIFs, but cannot afford $10,000 to
enhance a non-critical utility.
 
[3] System log file records for console messages also
include console commands.  CMSG logs these, and shows who
issued the console command (we ALLOW a lot of folks alot of
console commands, so this CMSG feature is useful for
tracking down who screwed what up).  I'd like to have the
option of having this information displayed to the console
as well as console messages, console requests and system
abort dumps messages ;->
 
 =======================================================================
Guy Smith                               Voice:   804-527-4000 ext 6664
Circuit City Stores, Inc.               FAX:     804-527-4116
9950 Mayland Drive                      E-Mail:  attmail.com!bronco!guys
Richmond, VA 23233-1464         Private E-Mail:  [log in to unmask]
 
The thoughts expressed herein are mine and do not reflect those of my
employer, or anyone with common sense.

ATOM RSS1 RSS2