Date: Sun, 28 Jan 2001 16:24:29 -0500 From: Andrew J Caines <A.J.Caines@altavista.net> To: freebsd-stable@freebsd.org Subject: Re: syslogd throwing a hissy fit Message-ID: <20010128162429.A412@hal9000.bsdonline.org> In-Reply-To: <20010124223705.A92362@gosset.maths.tcd.ie>; from dwmalone@maths.tcd.ie on Wed, Jan 24, 2001 at 10:37:05PM %2B0000 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Folks, Thanks to David Malone and Tony Byrne for their responses concerning this most most unusual syslogd behaviour. 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. 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. 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. I have made a bunch of related information available on my web site at <http://hal9000.bsdonline.org/tmp/>; 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: logmsg: pri 166, flags 16, from hal9000, msg 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> hal9000 /kernel: Jan 28 03:54:08 <console.info> hal90= 00 /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 /ke= rnel: Jan 28 03:54:07 <console.info> hal9000 /kernel: Jan 28 03:54:07 <cons= ole.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.in= fo> 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> ha= l9000 /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 <c= onsole.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 /ke= rnel: Jan 28=20 msg repeated 4 times, 0 sec of 30 msg repeated 4 times, 0 sec of 30 Assistance and recommendations are most welcome, as I am unhappy running without syslogd and am at a loss to address the problem. Thanks. -Andrew- --=20 _______________________________________________________________________ | -Andrew J. Caines- Unix Systems Engineer A.J.Caines@altavista.net | 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?20010128162429.A412>