From: Xin Zhao <uszhaoxin@gmail.com>
To: linux-os@analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: dumb question: How to create your own log files in a kernel module?
Date: Thu, 28 Apr 2005 16:59:21 -0400 [thread overview]
Message-ID: <4ae3c1405042813591f0b5962@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0504281557510.29750@chaos.analogic.com>
Thanks for kind help.
I know printk can do this job. But what I really want is to print logs
to a file specified by me instead of /var/log/messages. And, the
messages irrelevant to my module should not be written into that file.
Now my log mixed with other logs in /var/log/message, which bother me
much. :(
I guess the KERN_PRIVATE might work for this. Can you give me more details?
Thanks again!
Xin
On 4/28/05, Richard B. Johnson <linux-os@analogic.com> wrote:
> On Thu, 28 Apr 2005, Xin Zhao wrote:
>
> > Can anyone give me a hand? or point me to somewhere I can find related
> > information?
> >
> > Thanks in advance!
> >
> > Xin
>
> printk(KERN_XXX"whatever") was designed for this.
>
> #define KERN_EMERG "<0>" /* system is unusable */
> #define KERN_ALERT "<1>" /* action must be taken immediately */
> #define KERN_CRIT "<2>" /* critical conditions */
> #define KERN_ERR "<3>" /* error conditions */
> #define KERN_WARNING "<4>" /* warning conditions */
> #define KERN_NOTICE "<5>" /* normal but significant condition */
> #define KERN_INFO "<6>" /* informational */
> #define KERN_DEBUG "<7>" /* debug-level messages */
> printk(KERN_DEBUG fmt,##arg)
> printk(KERN_INFO fmt,##arg)
>
> You could define your own, KERN_PRIVATE "<8>" and have the syslog
> facility filter on that.
>
> Other ways are to write stuff to a buffer or linked-list and
> read it out using an ioctl() or read() in your module. If you
> do this, make sure that your module code doesn't wait forever
> if the buffer gets full.
>
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.6.11 on an i686 machine (5537.79 BogoMips).
> Notice : All mail here is now cached for review by Dictator Bush.
> 98.36% of all statistics are fiction.
>
next prev parent reply other threads:[~2005-04-28 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 18:10 dumb question: How to create your own log files in a kernel module? Xin Zhao
2005-04-28 20:06 ` Richard B. Johnson
2005-04-28 20:59 ` Xin Zhao [this message]
2005-04-28 22:00 ` Michael Opdenacker
2005-04-28 22:04 ` Chris Wedgwood
[not found] <3YlMk-iH-9@gated-at.bofh.it>
[not found] ` <3YnEA-1VB-27@gated-at.bofh.it>
[not found] ` <3YoqV-2JA-31@gated-at.bofh.it>
2005-04-28 23:28 ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
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=4ae3c1405042813591f0b5962@mail.gmail.com \
--to=uszhaoxin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
/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