From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: william fitzgerald <william.fitzgerald3@beer.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: printk performance logging without syslogd for router
Date: Tue, 13 Nov 2001 13:15:45 +0100 [thread overview]
Message-ID: <3BF10EF1.FD4075B6@loewe-komp.de> (raw)
In-Reply-To: <6169641FA9FA29E43946AEB269F1EA2E@william.fitzgerald3.beer.com>
william fitzgerald wrote:
>
> hi all,
>
> (perforamnce logging of network stack through a
> linux router)
>
> the main question:
>
> is there a way i can buffer or record the printk
> statements and print them to disk after my
> packets have gone through the router?
>
there is an option in syslogd to prevent immediatly
writing to the logfile:
prefix the log with a dash:
kern.* -/var/log/kernelmessages
next prev parent reply other threads:[~2001-11-13 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 12:07 printk performance logging without syslogd for router william fitzgerald
2001-11-13 12:15 ` Peter Wächtler [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-13 12:33 william fitzgerald
2001-11-13 12:35 ` Peter Wächtler
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=3BF10EF1.FD4075B6@loewe-komp.de \
--to=pwaechtler@loewe-komp.de \
--cc=linux-kernel@vger.kernel.org \
--cc=william.fitzgerald3@beer.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