mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Frank <mhf@users.berlios.de>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Alternatives to serial console for oops.
Date: Sun, 27 Nov 2005 21:04:30 +0100	[thread overview]
Message-ID: <20051127200758.2EED91C6B@hornet.berlios.de> (raw)
In-Reply-To: <4389D63B.4000702@superbug.demon.co.uk>

On Sunday 27 November 2005 16:52, James Courtier-Dutton 
wrote:
> Hi,
>
> I wish to view the oops that are normally output on the
> serial port of the PC. The problem I have, is that my PC
> does not have a serial port. Are there any alternatives
> for getting that vital oops from the kernel just as it
> crashes apart from the serial console. Could I get it to
> use some other interface? e.g. Network interface.
> Parallel port is also not an option.
>
> James

I use Netconsole for routine monitoring.

See Documentation/networking/netconsole.txt

Example for kernel command line
netconsole=1024@192.168.2.131/eth0,4450@192.168.2.1/00:00:0E:5F:15:64

You don't want to hassle with netcat.

Many sysloggers can log udp

I use syslog-ng. Excerpts from configuration:

source netlog { 
	udp(ip(0.0.0.0) port(4450)); 
};

destination netlog
{ 
	file("/var/log/netlog"); 
};

log 
{ 
	source(netlog); 
	destination("netlog"); 
	flags(final); 
};



  parent reply	other threads:[~2005-11-27 20:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-27 15:52 James Courtier-Dutton
2005-11-27 16:20 ` Willy Tarreau
2005-11-27 17:09 ` Jesper Juhl
2005-11-27 17:15   ` Mateusz Berezecki
2005-11-28 10:02     ` Geert Uytterhoeven
2005-11-28 13:10       ` Jan-Benedict Glaw
2005-11-27 18:30   ` Michael Tokarev
2005-11-27 20:04 ` Michael Frank [this message]
2005-11-28  4:48 ` Randy.Dunlap

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=20051127200758.2EED91C6B@hornet.berlios.de \
    --to=mhf@users.berlios.de \
    --cc=James@superbug.demon.co.uk \
    --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®