Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!mips!sgi!shinobu!odin!anchor!olson
From: olson@anchor.esd.sgi.com (Dave Olson)
Newsgroups: comp.sys.sgi
Subject: Re: duplicate SYSLOG messages on grcond exit
Message-ID: <1990Dec7.190603.26272@odin.corp.sgi.com>
Date: 7 Dec 90 19:06:03 GMT
References: <1990Dec4.193643.15115@unixg.ubc.ca> <1990Dec7.172945.24123@odin.corp.sgi.com>
Sender: news@odin.corp.sgi.com (Net News)
Organization: Silicon Graphics, Inc.  Mountain View, CA
Lines: 20

| In <1990Dec4.193643.15115@unixg.ubc.ca> laplante@ocgy.ubc.ca (Denis Laplante) writes:


|    When grcond exits, a duplicate copy of old unix (kernel) messages
|    appears in /usr/adm/SYSLOG.  The duplicates seem to include a complete
|    retrospective of messages from the kernel since the last reboot.
|    For example, I have copied here 2 sets of lines from /usr/adm/SYSLOG.
| 
|    NOTE: I am NOT looking for an explanation of the individual messages.
|    I want to find out how to stop bogus duplicate messages from
|    appearing in SYSLOG.

Actually, it is only the last 2K worth of the kernel circular buffer.
Unfortunately, their is no straightforward way to stop this.  As some
consolation, it will be fixed in the next major release...
--

	Dave Olson

Life would be so much easier if we could just look at the source code.