linux-kernel - Kernel 2.6.22-rc4 netconsole & syslogd bug

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 6 Jun 2007 18:00:10 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	linux-kernel@...r.kernel.org
Subject: Kernel 2.6.22-rc4 netconsole & syslogd bug

1. I use netconsole on almost all of my machines.
2. When I reboot one of them, it sends the kernel messages to the console
    logging server.
3. However, whenever I reboot it spams the console and every xterm open
    with the following:

Message from syslogd@p34 at Wed Jun  6 17:43:10 2007 ...
p34 sdb3>

Message from syslogd@p34 at Wed Jun  6 17:43:10 2007 ...
p34 sda3>

Message from syslogd@p34 at Wed Jun  6 17:43:10 2007 ...
p34 sdb2>

Message from syslogd@p34 at Wed Jun  6 17:43:10 2007 ...
p34 sda2>

Message from syslogd@p34 at Wed Jun  6 17:43:10 2007 ...
p34 sdb1>

Message from syslogd@p34 at Wed Jun  6 17:43:10 2007 ...
p34 sda1>

I also tried:

# Send p34 messages to their own file.
@192.168.0.1        /var/log/p34.log

But no luck here either.

Do I need to be running some sort of special netconsole server and send to 
a different port to avoid this spam?

Justin.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/