Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!eagle!ariel.lerc.nasa.gov!edwill
From: edwill@ariel.lerc.nasa.gov (Glenn L. Williams)
Newsgroups: comp.sys.apollo
Subject: Re: Apollo Miscellany
Message-ID: <1991Jun7.132148.8266@eagle.lerc.nasa.gov>
Date: 7 Jun 91 13:19:02 GMT
References: <9106051253.AA01516@pan.ssec.honeywell.com> <dennis.676156123@woodstock>
Sender: news@eagle.lerc.nasa.gov
Reply-To: edwill@ariel.lerc.nasa.gov
Organization: NASA Lewis Research Center
Lines: 22
News-Software: VAX/VMS VNEWS 1.3-4

In article <dennis.676156123@woodstock>, dennis@nosc.mil (Dennis Cottel) writes...
>John Thompson asks:
>> Does anyone _NOT_ use lsyserr?
> 
>This rang a bell for me, so just for fun I looked up the details.
> 
>Some time ago, I was trying to write a system watching program that
>would determine when the last error on a node took place and what the
>error was.  Because of the format of the lsyserr output, it takes some
>contortions even with Perl to figure this out.  In June 1988 I sent in
>an APR asking that the output of lsyserr be made more compatible with
>automated scanning.  In June of 1989 I got a reply stating "this has
>already been answered and was stamped 'to impl' for SR11".
> 
>I'm still waiting...  ;-)
> 
>   Dennis Cottel, dennis@NOSC.MIL, (619) 553-1645  
>   Naval Ocean Systems Center, San Diego, CA  92152

Try using grep (either BSD4.3 or SYSV.3) and pipe into it the output
of lsyserr, then search for the text you want using the grep parameters.
You can even do this from AEGIS (using /bin/grep).