Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!bionet!arisia!sgi!shinobu!odin!kestrel.sgi.com!paulm
From: paulm@kestrel.sgi.com (Paul Mielke)
Newsgroups: comp.sys.sgi
Subject: Re: SYSLOG
Message-ID: <2622@odin.SGI.COM>
Date: 9 Jan 90 17:49:06 GMT
References: <10319@alice.UUCP>
Sender: news@odin.SGI.COM
Reply-To: paulm@kestrel.sgi.com (Paul Mielke)
Organization: Silicon Graphics, Inc.
Lines: 16

In article <10319@alice.UUCP>, andrew@alice.UUCP (Andrew Hume) writes:
> 
> 
> has anyone running 3.2 (or 3.2.1) persuaded the syslog system to
> log disk errors? despite the obvious and default conf file,
> nothing gets logged but some whining by some networking daemons.
> i wrote a user program to log stuff; it worked.

In 3.2 and earlier software, the only stuff that goes into the syslog is
from user level programs that call syslog(3).  In a subsequent system
release, all kernel printfs (which will include error messages from disk
drivers) will also go to the syslogd.

Paul Mielke                  paulm@sgi.com
Advanced Systems Division    (415) 962-3447
Silicon Graphics, Inc.