From owner-freebsd-questions Mon Feb 3 00:27:38 1997 Return-Path: <owner-questions> Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA15130 for questions-outgoing; Mon, 3 Feb 1997 00:27:38 -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 AAA15125 for <questions@FreeBSD.org>; Mon, 3 Feb 1997 00:27:35 -0800 (PST) Received: from freebie.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0vrJkF-000QZoC; Mon, 3 Feb 97 09:27 MET Received: (grog@localhost) by freebie.lemis.de (8.8.4/8.6.12) id JAA23458; Mon, 3 Feb 1997 09:25:30 +0100 (MET) From: grog@lemis.de Message-Id: <199702030825.JAA23458@freebie.lemis.de> Subject: Re: syslogd runaway on 2.2-BETA In-Reply-To: <Pine.UW2.3.95.970202164445.3403C-100000@cedb> from Dan Busarow at "Feb 2, 97 05:21:41 pm" To: dan@dpcsys.com (Dan Busarow) Date: Mon, 3 Feb 1997 09:25:30 +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.de (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: > Hi, > > I just installed 2.2-BETA on a system with an AMD-K75, 8MB RAM ... > > top shows syslogd chewing up 99+ % of the CPU > top: > last pid: 170; load averages: 0.99, 0.89, 0.53 17:15:59 > 9 processes: 3 running, 6 sleeping > CPU states: 16.4% user, 0.0% nice, 83.0% system, 0.7% interrupt, 0.0% idle > 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? Does syslogd print any messages when it starts? Try stopping it and restarting it to find 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. Greg