From owner-freebsd-questions  Wed Feb  5 01:41:21 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id BAA01450
          for questions-outgoing; Wed, 5 Feb 1997 01:41:21 -0800 (PST)
Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id BAA01330
          for <questions@FreeBSD.org>; Wed, 5 Feb 1997 01:40:58 -0800 (PST)
From: Greg Lehey <grog@lemis.com>
Received: from freebie.lemis.com by diablo.ppp.de with smtp
	(Smail3.1.28.1 #1) id m0vs3oQ-000Qa0C; Wed, 5 Feb 97 10:38 MET
Received: (grog@localhost) by freebie.lemis.com (8.8.4/8.6.12) 
       id KAA24109; Wed, 5 Feb 1997 10:31:54 +0100 (MET)
Message-Id: <199702050931.KAA24109@freebie.lemis.com>
Subject: Re: syslogd runaway on 2.2-BETA
In-Reply-To: <Pine.UW2.3.95.970203084146.16779C-100000@cedb> from Dan Busarow at "Feb 3, 97 08:56:47 am"
To: dan@dpcsys.com (Dan Busarow)
Date: Wed, 5 Feb 1997 10:31:54 +0100 (MET)
Cc: questions@FreeBSD.org (FreeBSD Questions)
Organisation: 	LEMIS, Schellnhausen 2, 36325 Feldatal, Germany
Phone: +49-6637-919123
Fax: +49-6637-919122
Reply-to: grog@lemis.com (Greg Lehey)
WWW-Home-Page: http://www.FreeBSD.org/~grog
X-Mailer: ELM [version 2.4ME+ PL28 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

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