From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug server/20557] It seems like that switching output file doesn't work.
Date: Tue, 06 Sep 2016 18:51:00 -0000 [thread overview]
Message-ID: <bug-20557-6586-gsFVqHCS5c@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-20557-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20557
--- Comment #3 from David Smith <dsmith at redhat dot com> ---
Just to be clear, here is how this is supposed to work:
1) Run 'stap -F ...'. Systemtap will run in the background, outputting data
files. It prints the pid of the background stap process.
# stap -F -o f.out -S 1,3 ../src/testsuite/systemtap.base/flightrec2.stp
31067
2) System will output up to 3 (in my case) files of around 1 megabyte each. As
soon as the 4th file would be written, it deletes the earliest file.
After waiting a while, I see:
# ls -l f.out*
-rw-rw-r--. 1 dsmith dsmith 1034000 Sep 6 13:33 f.out.71
-rw-rw-r--. 1 dsmith dsmith 1034000 Sep 6 13:33 f.out.72
-rw-rw-r--. 1 dsmith dsmith 517000 Sep 6 13:33 f.out.73
then later:
# ls -l f.out*
-rw-rw-r--. 1 dsmith dsmith 1034000 Sep 6 13:35 f.out.175
-rw-rw-r--. 1 dsmith dsmith 1034000 Sep 6 13:35 f.out.176
-rw-rw-r--. 1 dsmith dsmith 770000 Sep 6 2016 f.out.177
3) To stop systemtap, kill the pid output earlier.
# kill 31067
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-09-06 18:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 3:05 [Bug server/20557] New: " steve.tsai at nexusguard dot com
2016-09-06 5:46 ` [Bug server/20557] " steve.tsai at nexusguard dot com
2016-09-06 18:31 ` dsmith at redhat dot com
2016-09-06 18:51 ` dsmith at redhat dot com [this message]
2016-09-06 19:38 ` dsmith at redhat dot com
2016-09-07 2:46 ` steve.tsai at nexusguard dot com
2016-09-07 2:49 ` steve.tsai at nexusguard dot com
2016-09-07 2:49 ` steve.tsai at nexusguard dot com
2016-09-07 14:17 ` dsmith at redhat dot com
2016-09-07 20:23 ` dsmith at redhat dot com
2016-09-08 2:04 ` steve.tsai at nexusguard dot com
2016-09-08 15:24 ` dsmith at redhat dot com
2016-09-09 2:16 ` steve.tsai at nexusguard dot com
2016-09-09 2:16 ` steve.tsai at nexusguard dot com
2016-09-09 2:19 ` steve.tsai at nexusguard dot com
2016-09-09 2:20 ` steve.tsai at nexusguard dot com
2016-09-09 2:20 ` steve.tsai at nexusguard dot com
2016-09-09 2:21 ` steve.tsai at nexusguard dot com
2016-09-09 13:45 ` dsmith at redhat dot com
2024-02-21 13:26 ` fche at redhat dot com
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=bug-20557-6586-gsFVqHCS5c@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).