Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: munnari!anu.anu.oz.au!mbl900@uunet.uu.net (Mathew B Lim)
Newsgroups: comp.sys.sun
Subject: syslogd
Message-ID: <8812130004.AA26573@uunet.UU.NET>
Date: 20 Dec 88 09:27:30 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 13
Approved: Sun-Spots@rice.edu
Original-Date: Mon, 12 Dec 88 14:44:25 est
X-Sun-Spots-Digest: Volume 7, Issue 64, message 4 of 12

Hi there,

We had the same trouble with our SUN 4. Try editing the file
/etc/syslog.conf and commenting out the line
	mail.debug ....... etc.
this works for us. I suspect (although I am not 100% sure that this is a
proper fix) that your machine is a standalone machine but has not been
told that it is it's own loghost. Thus it tries to send some log messages
(e.g. mail.debug messages) to an unknown `loghost' creating some sort of
loop. Does this make sense? Anyway try the above fix and test it. (To
test, try sending mail somewhere, this should send the syslogd wild if the
above fix has not been done). Oh yes, after editing /etc/syslog.conf, you
should kill syslogd and restart it.