From: Andreas Dilger <adilger@turbolabs.com>
To: Pekka Savola <pekkas@netcore.fi>
Cc: Ingo Molnar <mingo@elte.hu>, "Randy.Dunlap" <rddunlap@osdlab.org>,
linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
netdev@oss.sgi.com
Subject: Re: [patch] netconsole-2.4.10-B1
Date: Sat, 29 Sep 2001 16:37:00 -0600 [thread overview]
Message-ID: <20010929163659.J930@turbolinux.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0109291146440.1715-100000@localhost.localdomain> <Pine.LNX.4.33.0109291936500.17020-100000@netcore.fi>
In-Reply-To: <Pine.LNX.4.33.0109291936500.17020-100000@netcore.fi>
On Sep 29, 2001 19:40 +0300, Pekka Savola wrote:
> 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 don't expect a crash (ie:
> no listener in local network), but do log on remote syslogd's
> considerably.
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 sent to syslog,
and for some reason, even though I have LOG_KERN as the type, it only
gets logged to /var/log/messages and not /var/log/kern.log (on my system
at least) (this was in the TODO list, which I'm not in the position to
work on right now).
For crash dumps and such (which you don't want sent to syslog) it may be
useful to have a different message type (with its own offset numbers),
so the client knows to save it to a different file, for example, and will
handle out-of-order messages, and sparse memory dumps.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-09-29 22:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 20:04 [patch] netconsole - log kernel messages over the network. 2.4.10 Ingo Molnar
2001-09-26 19:36 ` Marcelo Tosatti
2001-09-26 21:15 ` jamal
2001-09-27 5:45 ` Ingo Molnar
2001-09-26 21:29 ` Andreas Dilger
2001-09-26 23:46 ` Andreas Dilger
2001-09-27 5:28 ` Ingo Molnar
2001-09-27 6:38 ` [patch] netconsole-2.4.10-B1 Ingo Molnar
2001-09-28 7:08 ` Andreas Dilger
2001-09-29 1:34 ` Randy.Dunlap
2001-09-29 9:52 ` Ingo Molnar
2001-09-29 16:32 ` John Alvord
2001-09-29 16:40 ` Pekka Savola
2001-09-29 22:37 ` Andreas Dilger [this message]
2001-09-30 3:38 ` Kenneth Johansson
2001-09-30 7:52 ` Rik van Riel
2001-09-30 10:40 ` Riley Williams
2001-09-30 10:48 ` Glynn Clements
2001-09-30 12:25 ` Richard Gooch
2001-10-01 7:35 ` Ingo Molnar
2001-10-01 14:55 ` Oliver Xymoron
2001-10-01 16:28 ` Richard Gooch
2001-10-01 8:47 ` Henning P. Schmiedehausen
2001-10-01 16:03 ` Andreas Dilger
2001-09-30 21:18 ` H. Peter Anvin
2001-09-30 16:00 ` Marcus Sundberg
2001-10-01 7:39 ` Ingo Molnar
2001-09-30 19:42 ` Randy.Dunlap
2001-09-30 20:25 ` Randy.Dunlap
2001-10-01 4:09 ` Andreas Dilger
2001-10-03 1:09 ` [patch] netconsole-2.4.10-C2 Randy.Dunlap
2001-10-01 16:58 ` [patch] netconsole-2.4.10-B1 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=20010929163659.J930@turbolinux.com \
--to=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
--cc=rddunlap@osdlab.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