From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel log mechanism: How to log messages in a different file
Date: Sun, 26 Jun 2011 03:05:35 +0700 [thread overview]
Message-ID: <BANLkTikFEhEW6wviH7YMs1HCaSR6JO4czQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikO6b6hi0i1KOzQ4A_w4Lb5v7yCkg@mail.gmail.com>
On Sat, Jun 25, 2011 at 20:40, amit mehta <gmate.amit@gmail.com> wrote:
> Hi,
>
> I've written some kernel modules using kprobes infrastructure
> to grab some more information on network packets. I've lots of
> printk which by default show up in syslog file(/var/log/messages),
> I was wondering if there are some method to redirect my printkS
> to appear in somewhere else(say /var/log/netlog).
> On a busy system, it gets little cluttered with other logs. Of-course
> i can grep for my own custom messages but it would be lot more
> convenient if i can redirect my messages in ?a separate log file.
side speaking, consider using netlink and create a user space netlink
grabber specificly to read the messages that thrown in your netlink
channel. IMO that would be faster and not cluttering the syslog
buffer...especially if you need to save tons of messages.....just my $
0.002 tips :D
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next prev parent reply other threads:[~2011-06-25 20:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-25 13:40 Kernel log mechanism: How to log messages in a different file amit mehta
2011-06-25 13:49 ` Bruce Rowen
2011-06-25 15:06 ` amit mehta
2011-06-25 20:05 ` Mulyadi Santosa [this message]
2011-06-27 16:57 ` Ramesh.P
2011-06-30 5:12 ` अनुज
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=BANLkTikFEhEW6wviH7YMs1HCaSR6JO4czQ@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).