Re: [patch] netconsole-2.4.10-B1

Randy.Dunlap (rddunlap@osdlab.org)
Fri, 28 Sep 2001 18:34:08 -0700


Andreas Dilger wrote:
>
> On Sep 27, 2001 08:38 +0200, Ingo Molnar wrote:
> > the patch also includes Andrew Morton's suggestion to add the
> > HAVE_POLL_CONTROLLER define for easier network-driver integration. The
> > eepro100.c changes now use this define.
> >
> > the new utilities-tarball is at:
> >
> > http://redhat.com/~mingo/netconsole-patches/netconsole-client-20010927.tar.gz
>
> A few minor changes to the code, after testing it a bit locally (note that I
> am using kernel patch C1):

[snip]

> Finally, a patch to netconsole-client.c which does a few things:
> - remove "offset" from output, it appears meaningless and screws formatting.
> - allow the client to receive messages from multiple servers, unless a
> single server is specified.

> TODO: allow client/server to be specified by both hostname/IP
> TODO: allow different client/server port numbers? Do we care?

Hi,

I hope to be able to use this, but...

I must admit that I'm confused by the terms server, client, and
target.

1. This is what I first thought:

server = the logging machine, client = machine under test,
and that "target" = client?

2. Then I was told this:
target == the machine to log to (== logging server)

so I thought that if the target is the server, then the client
must run on the machine under test. But the client program
won't be started early enough during boot for that to help me.

3. Then I was told this:
netconsole-client is the server
and
mingo should rename it ;-)

4. And finally this:
netconsole-client == target
kernel == source

WHOA! Stop the presses. Can someone say this more clearly,
and I'd suggest not using 3 names when 2 will do (probably
get rid of "target" and use client/server, or use some
other terminology).

~Randy
-
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/