Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!oliveb!pyramid!ncc!alberta!idacom!danny
From: danny@idacom.UUCP (Danny Wilson)
Newsgroups: comp.sys.apollo
Subject: /etc/syslog goes wild??
Keywords: SR9.7
Message-ID: <674@idacom.UUCP>
Date: 29 May 89 07:05:18 GMT
Organization: IDACOM Electronics Ltd., Edmonton, Alta.
Lines: 26

We are running SR9.7 Aegis with Domain/IX (BSD4.2).
Every once in a while I notice that the syslog process is consuming
CPU time like crazy (up to 90% as reported by dspst).

Both /bin/ps and /com/pst show that something is really 
happening there.

Our /etc/syslog.conf contains '1*/dev/log', so trying to 'catf'
/dev/log results in:

	Error: unable to open file "log" - system (or process) crash 
	prevented complete file close.

(or something like that...)

Has anyone seen this before? How do I fix it? (Is it really worth
running syslog at all?)

The answers to these questions and more can (hopefully) be found...
_on_the_network_.

-- 
Danny Wilson
IDACOM Electronics		danny@idacom.uucp
Edmonton, Alberta		alberta!idacom!danny
C A N A D A