Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!PAN.SSEC.HONEYWELL.COM!thompson
From: thompson@PAN.SSEC.HONEYWELL.COM (John Thompson)
Newsgroups: comp.sys.apollo
Subject: re: Browsing through error logs
Message-ID: <9103200300.AA15710@pan.ssec.honeywell.com>
Date: 20 Mar 91 03:00:40 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 21



<<forwarded message>>
>      This may sound like a silly question, but how does one go about
> looking at the contents of /sys/node_data/system_logs/sys_error_log?
> Currently when I try to "read" the file I get:
> (CV) sys_error_log - requested object is in use from (stream manager/IOS)
That's because it's in use!  ;-)
It's also not in ASCII format, so it's a moot point to try and view it this
way.  You can, however, use '/systest/ssr_util/lsyserr' to look at it.
You can also add '-n nodeID' to view somebody else's.  (Note that this is
_not_ a fully supported command, so you can't do '-n //nodename' -- it must
be the hex nodeID.

-- jt --
John Thompson
Honeywell, SSEC
Plymouth, MN  55441
thompson@pan.ssec.honeywell.com

Me?  Represent Honeywell?  You've GOT to be kidding!!!