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,
>
> 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> hal9000 /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 <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> 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:
> Logging to CONSOLE /dev/console
> logmsg: pri 2, flags 17, from hal9000, msg 54:07 <console.info> hal9000 /kernel: Jan
>28
> 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-
> --
> _______________________________________________________________________
> | -Andrew J. Caines- Unix Systems Engineer [EMAIL PROTECTED] |
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
