Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!rpi!uwm.edu!bionet!agate!ucbvax!van-bc!ubc-cs!unixg.ubc.ca!ocgy.ubc.ca!laplante
From: laplante@ocgy.ubc.ca (Denis Laplante)
Newsgroups: comp.sys.sgi
Subject: Re: disk full message in SYSLOG
Message-ID: <1991Apr10.113918@ocgy.ubc.ca>
Date: 10 Apr 91 18:39:18 GMT
References: <9104091950.AA09095@poly1.nist.gov>
Sender: news@unixg.ubc.ca (Usenet News Maintenance)
Reply-To: laplante@ocgy.ubc.ca (Denis Laplante)
Organization: University of British Columbia, Vancouver, B.C., Canada
Lines: 14
Nntp-Posting-Host: nessie.ocgy.ubc.ca

In article <9104091950.AA09095@poly1.nist.gov>, rbriber@POLY1.NIST.GOV writes:
|> Here's what should be a simple question.  SYSLOG contains the following
|> error about once a day:
|> 
|> Apr  8 18:03:02 poly2 grcond[7495]: CIO: t of space
|> Apr  8 18:03:02 poly2 grcond[7495]: CIO: dks0d1s6: Out of space
|> Apr  8 18:03:02 poly2 last message repeated 16 times
|> 

You should ignore most messages in SYSLOG of the form 'grcond[....]: CIO' ,
as they are redundant copies of messages reported previously.
On the 3 SGI systems I know, similar spurious messages appear everytime
someone logs out.  I have an awk script to filter out uninteresting SYSLOG
messages.