[comp.sys.mips] wild syslogd

bin@primate.wisc.edu (Brain in Neutral) (10/17/90)

The past 2 days I've come in to find that my syslod has been chewing up
all the cpu since midnight.  This is when
/usr/adm/periodic/daily/10.syslogd.system is executed.  Upon further
invesigation, I find that sending -1 to syslogd (which is what */10.syslogd.*
does) now causes it to go into this state...

...which it never has before.  ???

RISC/os 4.01, M/120.
-- 
Paul DuBois
dubois@primate.wisc.edu

                 "Was all of this because I wore a big man's hat?"