Date: Wed, 5 Feb 1997 10:31:54 +0100 (MET) From: Greg Lehey <grog@lemis.com> To: dan@dpcsys.com (Dan Busarow) Cc: questions@FreeBSD.org (FreeBSD Questions) Subject: Re: syslogd runaway on 2.2-BETA Message-ID: <199702050931.KAA24109@freebie.lemis.com> In-Reply-To: <Pine.UW2.3.95.970203084146.16779C-100000@cedb> from Dan Busarow at "Feb 3, 97 08:56:47 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Dan Busarow writes: > On Mon, 3 Feb 1997, Greg Lehey wrote: >> Dan Busarow writes: >>> Mem: 3632K Active, 508K Inact, 1384K Wired, 696K Cache, 517K Buf, 696K Free >>> Swap: 26M Total, 64K Used, 25M Free >>> >>> PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND >>> 79 root 98 0 196K 552K RUN 11:24 99.22% 99.22% syslogd >> >> Strange. >> >> What does your /etc/syslog.conf look like? > > It was the stock 2.2-BETA_A issue. I've commented out the logging > to /dev/console and added *.err to /var/log/messages > >> Does syslogd print any >> messages when it starts? Try stopping it and restarting it to find > > It takes about 30 seconds before it detaches and then prints > syslogd: timed out waiting for child Hmm. You could try ktracing it and see what's going on. I wonder if it's getting uptight because it can't talk to the console. >> out. Make sure, of course, that the problem persists after you >> restart it. Also, if you have ktrace enabled in the kernel, check >> what it's doing. > > Still the same. I'll build a new kernel and give that a try. I doubt it's the kernel. Keep me posted. Greg
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702050931.KAA24109>