Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[patch\]\s+netconsole\-2\.4\.10\-B1\s*$/: 36 ]

Total 36 documents matching your query.

1. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: Ingo Molnar <mingo@xxxxxxx>
Date: Mon, 1 Oct 2001 09:35:47 +0200 (CEST)
'server' is the box that serves content. 'client' is one that requests and accepts it. in the case of netconsole, it's the netconsole-module box that produces the messages, and the other one gets the
/archives/netdev/2001-10/msg00000.html (9,588 bytes)

2. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: Oliver Xymoron <oxymoron@xxxxxxxxx>
Date: Mon, 1 Oct 2001 09:55:39 -0500 (CDT)
Server is the side providing the service - direction of data is irrelevant. If the service is logging, the side doing the logging is the server. If the service is console message generation, then the
/archives/netdev/2001-10/msg00004.html (8,695 bytes)

3. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: Richard Gooch <rgooch@xxxxxxxxxxxxxxx>
Date: Mon, 1 Oct 2001 10:28:24 -0600
Hey! I didn't call anyone stupid. I didn't even call the idea stupid. I think your terminology is backwards to the way I think and what seems to be accepted practice (and I notice I'm not alone in th
/archives/netdev/2001-10/msg00005.html (8,704 bytes)

4. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: "Randy.Dunlap" <rddunlap@xxxxxxxxxx>
Date: Mon, 01 Oct 2001 09:58:07 -0700
Not quite for formatting, but NIPQUAD(ipaddr) passes 4 octets of IP address to <anywhere>. Here's a patch/replacement for the IP address printing in the netconsole kernel module, using NIPQUAD(). Aga
/archives/netdev/2001-10/msg00006.html (10,276 bytes)

5. [patch] netconsole-2.4.10-B1 (score: 1)
Author: <mingo@xxxxxxx>
Date: Thu, 27 Sep 2001 08:38:51 +0200 (CEST)
yep, that is very useful indeed. i've implemented a private emergency pool of 32 packets that we try to keep filled as much as possible, and which one we use only if GFP_ATOMIC fails. The new patch c
/archives/netdev/2001-09/msg00119.html (11,081 bytes)

6. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: xxxxxxxxxxxxxx>
Date: Fri, 28 Sep 2001 01:08:19 -0600
A few minor changes to the code, after testing it a bit locally (note that I am using kernel patch C1): First, a patch to change the MAC address kernel parameter to be in the standard XX:XX:XX:XX:XX:
/archives/netdev/2001-09/msg00124.html (26,362 bytes)

7. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: @xxxxxxxxxxxxx>
Date: Fri, 28 Sep 2001 18:34:08 -0700
[snip] 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 = machin
/archives/netdev/2001-09/msg00125.html (11,864 bytes)

8. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: lap@xxxxxxxxxx>
Date: Sat, 29 Sep 2001 09:32:00 -0700 (PDT)
Would this scheme work for crash dump capturing? john
/archives/netdev/2001-09/msg00126.html (10,887 bytes)

9. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: jalvo@xxxxxxxx>
Date: Sat, 29 Sep 2001 19:40:27 +0300 (EEST)
Speaking of which, would it be too big a burden (or is it supported already), that the oopses or dumps would be sent off to an off-link syslog server? This would ease the use in occasions where you d
/archives/netdev/2001-09/msg00127.html (10,245 bytes)

10. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: kas@xxxxxxxxxx>
Date: Sat, 29 Sep 2001 16:37:00 -0600
That was in the patch I just sent to Ingo - the "client" logs all of the messages to syslog. However, it is not "perfect" yet, in that you need to be able to select whether or not you really want it
/archives/netdev/2001-09/msg00128.html (11,810 bytes)

11. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: @xxxxxxxxxxxxx>
Date: Sat, 29 Sep 2001 11:52:43 +0200 (CEST)
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 ho
/archives/netdev/2001-09/msg00129.html (10,613 bytes)

12. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: <mingo@xxxxxxx>
Date: Sun, 30 Sep 2001 05:38:20 +0200
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 wh
/archives/netdev/2001-09/msg00130.html (10,496 bytes)

13. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: <ken@xxxxxxxx>
Date: Sun, 30 Sep 2001 04:52:49 -0300 (BRST)
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.
/archives/netdev/2001-09/msg00131.html (10,501 bytes)

14. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: xxxxxxxxxxxxxx>
Date: Sun, 30 Sep 2001 11:48:46 +0100
... 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 prob
/archives/netdev/2001-09/msg00132.html (10,983 bytes)

15. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: nts@xxxxxxxxxx>
Date: Sun, 30 Sep 2001 06:25:33 -0600
Let's see, with X, the server is local (at least, it's local to where I've placed my ass) and the client is remote. I usually think of "server" as the box that's running all the time, providing a ser
/archives/netdev/2001-09/msg00133.html (10,328 bytes)

16. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: xxxxxxxxxxxxxx>
Date: Sun, 30 Sep 2001 12:42:09 -0700
Thanks for the definitions. I can work with them, although I think that there's much room for improvement... ~Randy
/archives/netdev/2001-09/msg00134.html (9,807 bytes)

17. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: lap@xxxxxxxxxx>
Date: Sun, 30 Sep 2001 13:25:59 -0700
and I did. Eliminating typos on 'insmod netconsole.o ...' helps. :) Here's 3c59x.c patched for netconsole (HAVE_POLL_CONTROLLER). Ingo, you _are_ planning to use most or all of Andreas's patches, are
/archives/netdev/2001-09/msg00135.html (10,727 bytes)

18. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: lap@xxxxxxxxxx>
Date: Sun, 30 Sep 2001 22:09:50 -0600
I was thinking about this as well. It should be relatively easy to allow a line line "console=eth0,XX:XX:XX:XX:XX:XX,a.b.c.d" or similar. The only slight problem might be in configuring the interface
/archives/netdev/2001-09/msg00136.html (10,240 bytes)

19. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: Ingo Molnar <mingo@xxxxxxx>
Date: Mon, 1 Oct 2001 09:35:47 +0200 (CEST)
'server' is the box that serves content. 'client' is one that requests and accepts it. in the case of netconsole, it's the netconsole-module box that produces the messages, and the other one gets the
/archives/netdev/2001-10/msg00238.html (9,649 bytes)

20. Re: [patch] netconsole-2.4.10-B1 (score: 1)
Author: Oliver Xymoron <oxymoron@xxxxxxxxx>
Date: Mon, 1 Oct 2001 09:55:39 -0500 (CDT)
Server is the side providing the service - direction of data is irrelevant. If the service is logging, the side doing the logging is the server. If the service is console message generation, then the
/archives/netdev/2001-10/msg00242.html (8,742 bytes)


This search system is powered by Namazu