From: Jeff Moyer <jmoyer@redhat.com>
To: "Jörn Engel" <joern@logfs.org>
Cc: linux-kernel@vger.kernel.org, Joel Becker <jlbec@evilplan.org>
Subject: Re: Announce: cancd 0.2.0 netconsole capture server
Date: Mon, 06 Feb 2012 16:31:14 -0500 [thread overview]
Message-ID: <x49mx8vps2l.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20120206190206.GA8068@logfs.org> (=?utf-8?Q?=22J=C3=B6rn?= Engel"'s message of "Mon, 6 Feb 2012 14:02:06 -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
next prev parent reply other threads:[~2012-02-06 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 19:02 Jörn Engel
2012-02-06 21:31 ` Jeff Moyer [this message]
2012-02-06 20:13 ` Jörn Engel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x49mx8vps2l.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=jlbec@evilplan.org \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®