From: Ming Zhang <blackmagic02881@gmail.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: log large amount of output
Date: Mon, 30 Apr 2007 14:25:00 -0000 [thread overview]
Message-ID: <1177943118.3864.10.camel@dhcp-84.ibrix.com> (raw)
Hi All
I wonder what is the best way to log large amount of printout.
I have a lot of debug text need to be saved for later analysis. My
current way is to print them out and when run stap, redirect the stdout
to a file. Is there a better way to achieve my goal with less overhead?
Thanks!
Ming
reply other threads:[~2007-04-30 14:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1177943118.3864.10.camel@dhcp-84.ibrix.com \
--to=blackmagic02881@gmail.com \
--cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).