Path: utzoo!attcan!uunet!lll-winken!cert!netnews.upenn.edu!rutgers!uwm.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!bin
From: bin@primate.wisc.edu (Brain in Neutral)
Newsgroups: comp.sys.mips
Subject: wild syslogd
Message-ID: <3293@uakari.primate.wisc.edu>
Date: 17 Oct 90 13:08:57 GMT
Organization: Cafe Limbo
Lines: 14

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?"