Messages in this thread | | | From | Jeff Moyer <> | Subject | Re: Announce: cancd 0.2.0 netconsole capture server | Date | Mon, 06 Feb 2012 16:31:14 -0500 |
| |
Jörn Engel <joern@logfs.org> writes:
> Quoting Documentation/networking/netconsole.txt: > The remote host can run either 'netcat -u -l -p <port>', > 'nc -l -u <port>' or syslogd. > > Now, both of these options have their issues. Netcat works fine, but > only reasonably scales to 1. Having to use a seperate port for every > test machine, as well as a seperate netcat process that writes to a > proper file becomes a bit of a nightmare by the time you approach > three digits of machines. > > Syslogd would be great, if netconsole actually spoke syslog protocol. > As it is netconsole speaks a protocol I would describe as "7bit ascii, > no nonsense". Syslog protocal is described in rfc5424, a 38-page > document. I think it is fair to say the two are incompatibel. In > case someone actually wants to see the full trainwreck, a quick search > should come up with enough bug reports to scare your children into > bed. > > Given that sad state of things, here is yet another alternative: > http://git.kernel.org/?p=linux/kernel/git/joern/cancd.git
Hmm, the old netdump-server package that we used to ship in RHEL should work too, I think, if you are interested in that approach. That was designed specifically to receive netconsole messages and netdumps from multiple servers. Google up netdump-server-0.7.16 and you should find an srpm. If there's interest in keeping that alive, I can put it up in some public repo.
Cheers, Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |