From: Larry Kessler <kessler@us.ibm.com>
To: linux-kernel mailing-list <linux-kernel@vger.kernel.org>
Cc: francois-xavier_kowalski@hp.com,
evlog-developers Mailing-List
<evlog-developers@lists.sourceforge.net>,
michel.dagenais@polymtl.ca
Subject: Re: [evlog-dev] Re: Event logging vs enhancing printk
Date: Wed, 10 Apr 2002 11:41:50 -0700 [thread overview]
Message-ID: <3CB4876E.EAF4DA71@us.ibm.com> (raw)
In-Reply-To: <3CB472BE.4030708@hp.com>
Francois-Xavier Kowalski wrote:
> I am currently working in the Telecom area (signalling), on systems that
> usually process several tenths of thousands of telephone calls per
> second, during years. So I am the kind of guy interrested in having
> enhancements to the Linux logging sub-systems
You did not say what Linux distribution(s) you "favor", but MontaVista
has announced that Event Logging, Linux Trace Toolkit, and some other
features you probably want will be included in their Carrier Grade
Edition,
Version 2.1.
See http://www.mvista.com/dswp/MVLCGE.pdf for details.
prev parent reply other threads:[~2002-04-10 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 17:13 Event logging vs enhancing printk Francois-Xavier Kowalski
2002-04-10 18:41 ` Larry Kessler [this message]
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=3CB4876E.EAF4DA71@us.ibm.com \
--to=kessler@us.ibm.com \
--cc=evlog-developers@lists.sourceforge.net \
--cc=francois-xavier_kowalski@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michel.dagenais@polymtl.ca \
/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