From owner-freebsd-stable Wed Jan 24 14:37:25 2001 Delivered-To: freebsd-stable@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 28F9837B400 for ; Wed, 24 Jan 2001 14:37:08 -0800 (PST) Received: from gosset.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 24 Jan 2001 22:37:06 +0000 (GMT) Date: Wed, 24 Jan 2001 22:37:05 +0000 From: David Malone To: Tony Byrne Cc: Andrew J Caines , freebsd-stable@freebsd.org Subject: Re: syslogd throwing a hissy fit Message-ID: <20010124223705.A92362@gosset.maths.tcd.ie> References: <20010121021039.A442@hal9000.bsdonline.org> <7q9u6t0tkj5ktplad6k8468koar3j8jvi9@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from tony@nua.ie on Wed, Jan 24, 2001 at 09:43:59PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 24, 2001 at 09:43:59PM +0000, Tony Byrne wrote: > My investigations using "syslogd -v" show that the all of the looped and > corrupt log lines that I am seeing are of the LOG_CONSOLE facility with > the 'info' priority. (console.info) (14.6) > > It's my guess that syslogd is entering a tight loop whenever syslog.conf > is configured so that a log message with facility LOG_CONSOLE is > directed to /dev/console. The committer seems to have been aware of the > problem, but maybe an incorrectly configured syslog.conf would > circumvent the checks within the code? There should be code to prevent this looping, as you point out. Can you send me the output of syslogd -d while it's looping and I'll try to figure out what is going on. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message