Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!olivea!samsung!think.com!hsdndev!dartvax!eleazar.dartmouth.edu!paw
From: paw@eleazar.dartmouth.edu (Pat Wilson)
Newsgroups: comp.unix.aix
Subject: Help!  Runaway syslogd...
Message-ID: <1991May1.192652.12002@dartvax.dartmouth.edu>
Date: 1 May 91 19:26:52 GMT
Sender: news@dartvax.dartmouth.edu (The News Manager)
Organization: Project NORTHSTAR
Lines: 21
Originator: paw@eleazar.dartmouth.edu


Pretty weird...

For the last two days I've had /etc/syslogd go nuts and start forking 
copies of itself (filling up the process table along the way).  I don't
_think_ I've changed anything lately that would affect syslogd...  The
trigger is unknown at the moment, and isn't anything obvious.  Has
anyone ever seen anything like this?  Any ideas where to start looking
for the cause?  I've rebooted (though not powered down) once since this 
started, but it hasn't cured the problem.  It only seems to be happening
on this one machine (I've got 14 320s, most of which are clones of the
machine having the problem).

I'm running 3003 on a 320 with 16Mb RAM and 64Mb swap.

Thanks.

-- 
Pat Wilson
Systems Manager, Project NORTHSTAR
paw@northstar.dartmouth.edu