Date: Wed, 24 Jan 2001 22:37:05 +0000 From: David Malone <dwmalone@maths.tcd.ie> To: Tony Byrne <tony@nua.ie> Cc: Andrew J Caines <A.J.Caines@altavista.net>, freebsd-stable@freebsd.org Subject: Re: syslogd throwing a hissy fit Message-ID: <20010124223705.A92362@gosset.maths.tcd.ie> In-Reply-To: <s7hu6torq3c79usoqpgig3b56gg9d5n6jr@4ax.com>; from tony@nua.ie on Wed, Jan 24, 2001 at 09:43:59PM %2B0000 References: <20010121021039.A442@hal9000.bsdonline.org> <7q9u6t0tkj5ktplad6k8468koar3j8jvi9@4ax.com> <s7hu6torq3c79usoqpgig3b56gg9d5n6jr@4ax.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010124223705.A92362>