Path: utzoo!utgpu!watmath!clyde!att!rutgers!ukma!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: ji@read.cs.columbia.edu (John Ioannidis)
Newsgroups: comp.sys.sun
Subject: Re: Syslogd is eating my CPU for breakfast
Message-ID: <8811230956.AA14755@read.cs.columbia.edu>
Date: 4 Dec 88 00:43:20 GMT
Sender: usenet@rice.edu
Organization: Rice University, Houston, Texas
Lines: 29
Approved: Sun-Spots@rice.edu
Original-Date: Wed, 23 Nov 88 04:56:35 EST
X-Sun-Spots-Digest: Volume 7, Issue 36, message 8 of 12

In article <2368@cloud9.UUCP> you write:
>X-Sun-Spots-Digest: Volume 7, Issue 21, message 4 of 12
>
>Syslogd sometimes, rather mysteriously starts consuming an inordinate
>amount of CPU time, to the extent of driving up my load averages to
>unbelievable levels...

RTFM!  I'm quoting from the SunOS Release 4.0 READ THIS FIRST, page 3:

7. The symbol LOGHOST is not correctly defined by syslogd on loghost
machines.  This results in 100% CPU usage and syslod accumulating
large amounts of CPU time.

To prevent this problem insert the following line at the beginning of
/etc/syslogd.conf on loghost machines:

	define(LOGHOST, 1)

[[ My thanks to everyone else who has sent in (or will send in) similar
information.  --wnl ]]

/ji

In-Real-Life: John "Heldenprogrammer" Ioannidis
Organization: GIP Altair [IN2-INRIA-LRI]
P-Address: Domaine de Voluceau, BP 105 / Rocquencourt 78153 Le Chesnay / France
V-Address: +33 1 39635417
E-Address: ...!mcvax!inria!bdblues!ji, ji@bdblues.altair.fr
Alt-E-Address: ji@cs.columbia.edu