lkml.org 
[lkml]   [2001]   [Sep]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch] netconsole-2.4.10-B1
Hi Rik.

>>> sorry :-) definitions of netconsole-terms:
>>>
>>> 'server': the host that is the source of the messages. Ie. the box that
>>> runs the netconsole.o module. It serves log messages to the
>>> client.
>>>
>>> 'client': the host that receives the messages. This box is running the
>>> netconsole-client.c program.

>> Servers is usually the thing waiting for something to be sent to it,
>> the client is the sending part(initiator). this works for web
>> servers, X servers, log servers but strangley not for netconsole
>> where everything is backwards.

> Owww crap. The majority of web traffic is _from_ the server _to_
> the client. Same for ftp, realaudio, etc...

> In fact, usually the server is the _remote_ machine and the client
> is the _local_ machine.

There's actually one example in the email you were replying to where the
server is the local machine and the client is the remote one, which you
must have overlooked: X-Windows defines the server as being the machine
with the display that it is to draw its picture on.

Perhaps I can offer a more reasonable definition than yours, and one
that is offered by most UK universities:

SERVER The system with some facility which other systems
wish to make use of.

CLIENT The system wishing to make use of some facility on
the server.

Apply that to the relevant protocols and you get the following table:

PROTOCOL SERVER CLIENT

Login - CHAP Local Remote
Login - PAP Local Remote
Login - SSH Local Remote
Login - Text Remote Local

FTP Remote Local
LogServer Remote Local
PrintServer Remote Local
RealAudio Remote Local
Web Remote Local

X-Windows Local Remote

NetConsole ??? ???

Note that under that definition, the server can be either the local or
the remote system, with a 3:2 bias towards it being the remote system. I
don't know NetConsole, so can't comment on how it uses them.

Also note that for one task (logging in) that can be done by four
different methods (that I am aware of), only one of those methods has
the server as the remote system. The CHAP, PAP and SSH login systems all
define the local machine (the one trying to log in) as being the one
having the private part of a public/private keypair, with both systems
having the public part, and therefore assume that the local system is
the server that will authenticate a message sent by the remote client to
verify that the server is the correct system and user. Only the text
login assumes the opposite.

> Anybody who believes in having the client remote and the server
> local should be shipped off to whereever the server is ;)

>From their point of view, they already are where the server is, so no
shipping is necessary.

Best wishes from Riley.

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

\
 
 \ /
  Last update: 2005-03-22 13:03    [W:0.170 / U:3.096 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site