Rik van Riel wrote: > > > 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... ... whereas with SMTP, syslog, printer (lpd) etc, it's the other way around. Some servers are primarily "sources", while others are primarily "sinks". Sources are more common, and most users are probably more familiar with sources than sinks. > In fact, usually the server is the _remote_ machine and > the client is the _local_ machine. But not for for X, NAS, ident ... Local is a relative term. Presumably you meant local relative to a user. There are all kinds of generalisations one could make about individual protocols, none of which are ultimately relevant to the client/server distinction. As Ingo points out, although it could have been more clear, the actual distinction between client and server is that the client initiates the communication, while the server responds (cf "originate" and "answer" in telephone terminology). -- Glynn Clements <glynn.clements@virgin.net> - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
