Newsgroups: comp.sys.sgi
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!mintaka!electron!andru
From: andru@electron.lcs.mit.edu (Andrew Myers)
Subject: Re: disk full message in SYSLOG
Message-ID: <1991Apr13.194244.13717@mintaka.lcs.mit.edu>
Sender: news@mintaka.lcs.mit.edu
Organization: MIT Laboratory for Computer Science
References: <9104091950.AA09095@poly1.nist.gov> <1991Apr10.113918@ocgy.ubc.ca>
Date: Sat, 13 Apr 91 19:42:44 GMT
Lines: 20

laplante@ocgy.ubc.ca (Denis Laplante) writes:
> rbriber@POLY1.NIST.GOV writes:
>|> 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.

Not true. A message of the form "grcond: [...] CIO: ..." is a message which
would have appeared on the console, if there had been a console. However,
this message was generated while there was no console to print it to,
either because the console window was closed, or because graphical login
is running.

Instead, the "graphics console daemon" (grcond) intercepted the message
and put it in SYSLOG. While the message may indeed be identical to
messages which were previously reported to the console or to SYSLOG,
it is not necessarily redundant.

Andrew