Date: Sun, 28 Jan 2001 18:48:01 -0500 From: Andrew BOGECHO <andrewb@cs.mcgill.ca> To: Andrew J Caines <A.J.Caines@altavista.net> Cc: freebsd-stable@FreeBSD.ORG Subject: Re: syslogd throwing a hissy fit Message-ID: <20010128184801.C16717@cs.mcgill.ca> In-Reply-To: <20010128162429.A412@hal9000.bsdonline.org>; from A.J.Caines@altavista.net on Sun, Jan 28, 2001 at 04:24:29PM -0500 References: <20010121021039.A442@hal9000.bsdonline.org> <7q9u6t0tkj5ktplad6k8468koar3j8jvi9@4ax.com> <s7hu6torq3c79usoqpgig3b56gg9d5n6jr@4ax.com> <20010124223705.A92362@gosset.maths.tcd.ie> <5qou6tkiba9jk6nbjepe9hn2g45hq560ep@4ax.com> <20010121021039.A442@hal9000.bsdonline.org> <7q9u6t0tkj5ktplad6k8468koar3j8jvi9@4ax.com> <s7hu6torq3c79usoqpgig3b56gg9d5n6jr@4ax.com> <20010124223705.A92362@gosset.maths.tcd.ie> <20010128162429.A412@hal9000.bsdonline.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Sun Jan 28 18:33:27 EST 2001 Hi Andrew, It has been happening to me only when I pipe things to /dev/console. Otherwise none of the messages show up. This unfortunately means that the perl script that I run to tail all.log and pipe info I want to /dev/console cannot be used as it continuously spits out the kernel messages. To test my theory further, just doing a tail -f /var/log/all.log > /dev/console and then slogin into the machine, or run an ls and it causes the same effect. Killing the tail sets everything back to quiet. I have tried cvsups from the 20th of Jan to the 26th, and this problem seems to occur each time. I even did a clean 4.2 install, but as soon as I did a cvsup to the latest stable, the problem reoccured. Any tips would be helpful. Andrew. On Sun, Jan 28, 2001 at 04:24:29PM -0500, Andrew J Caines wrote: > Folks, >=20 > Thanks to David Malone and Tony Byrne for their responses concerning this > most most unusual syslogd behaviour. >=20 > After the last cvsup on Thursday night, build and install there is no > change in the fit that syslogd throws when started. This is no surprise, > since there is nothing clearly related to syslog in the last update. >=20 > I have confirmed that this behaviour does not depend on the presence of > the new "console" facility enabled in syslog.conf, although the problem > clearly points to this new addition as a factor. Nor does the problem > depend on the arguments with which syslogd is invoked. >=20 > I am surprised to have not seen more people reporting this problem since > it occurred out of the blue in my fairly vanilla setup and is extremely > visible. >=20 > I have made a bunch of related information available on my web site at >=20 > <http://hal9000.bsdonline.org/tmp/>; >=20 > including my main config files, cvsup, build and install logs and a sample > output from running "syslog -d". Here's and extract from this output: >=20 > logmsg: pri 166, flags 16, from hal9000, msg Jan 28 03:54:08 <console.inf= o> hal9000 /kernel: Jan 28 03:54:08 <console.info> hal9000 /kernel: Jan 28 = 03:54:08 <console.info> hal9000 /kernel: Jan 28 03:54:08 <console.info> hal= 9000 /kernel: Jan 28 03:54:08 <console.info> hal9000 /kernel: Jan 28 03:54:= 07 <console.info> hal9000 /kernel: Jan 28 03:54:07 <console.info> hal9000 /= kernel: Jan 28 03:54:07 <console.info> hal9000 /kernel: Jan 28 03:54:07 <co= nsole.info> hal9000 /kernel: Jan 28 03:54:07 <console.info> hal9000 /kernel= : Jan 28 03:54:07 <console.info> hal9000 /kernel: Jan 28 03:54:07 <console.= info> hal9000 /kernel: Jan 28 03:54:07 <console.info> hal9000 /kernel: Jan = 28 03:54:07 <console.info> hal9000 /kernel: Jan 28 03:54:07 <console.info> = hal9000 /kernel: Jan 28 03:54:07 <console.info> hal9000 /kernel: Jan 28 03:= 54:07 <console.info> hal9000 /kernel: Jan 28 03:54:07 <console.info> hal900= 0 /kernel: Jan 28 03:54:07 <console.info> hal9000 /kernel: Jan 28 03:54:07 = <console.info> hal9000 /kernel: Jan 28 03:54:07 < > console.info> hal9000 /kernel: Jan 28 03: > Logging to CONSOLE /dev/console > logmsg: pri 2, flags 17, from hal9000, msg 54:07 <console.info> hal9000 /= kernel: Jan 28=20 > msg repeated 4 times, 0 sec of 30 > msg repeated 4 times, 0 sec of 30 >=20 >=20 > Assistance and recommendations are most welcome, as I am unhappy running > without syslogd and am at a loss to address the problem. >=20 >=20 > Thanks. >=20 >=20 > -Andrew- > --=20 > _______________________________________________________________________ > | -Andrew J. Caines- Unix Systems Engineer A.J.Caines@altavista.net | >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message 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?20010128184801.C16717>