From: khandelw@cs.fsu.edu
To: linux-kernel@vger.kernel.org
Subject: logging in kernel
Date: Fri, 26 Mar 2004 17:24:35 -0500 [thread overview]
Message-ID: <1080339875.8f2cd36818efd@system.cs.fsu.edu> (raw)
Hello,
I am a graudate student at Florida State University. My friends and my self
are planning to implement a kernel logger for linux kernel (real-time systems).
We are new to linux kernel programming and we have not done kernel programming.
We believe right now most of the system are using printk. We want to write a
tool which can be used for debugging as well as logging of data in the future.
Following are the things that we have in mind so far.
1. Implement the logging daemon or the server as a periodic task in the
real-time system.
2. Have an api which looks similar to printk
3. Have an option to specify the write the network card or console or a
dedicated device.
4. Use it for checkpointing in distributed system.
I am not sure whether such a tool is required but I believe it will give me a
taste of kernel programming.
Any suggestions would be highly appreciated.
Thanking you all in anticipation.
-- Amit Khandelwal
next reply other threads:[~2004-03-26 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 22:24 khandelw [this message]
2004-03-27 5:53 ` logging in kernel Karim Yaghmour
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=1080339875.8f2cd36818efd@system.cs.fsu.edu \
--to=khandelw@cs.fsu.edu \
--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