From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug testsuite/28958] Current git + RHEL (4.18.0) has 3 working NFSd examples, and one broken.
Date: Fri, 25 Mar 2022 20:02:30 +0000 [thread overview]
Message-ID: <bug-28958-6586-KJJE0uhKSE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28958-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28958
--- Comment #6 from William Cohen <wcohen at redhat dot com> ---
Glad that the nfsd-trace.stp is working for you.
Do you have some repository for the scripts processing the output of the
systemtap scripts?
Not sure what would be the best way to make the supplemental scripts
functionality available to others. Some possibilities:
-Add a directory in testsuite/systemtap.examples to hold the processing
scripts, maybe something like the the lwtools directoy
-Add an entry to the wiki at https://sourceware.org/systemtap/wiki describing
the scripts, where to get them, and how to use them.
-Update existing systemtap script to include the functionality. The examples
allow using shell scripts.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-03-25 20:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 19:06 [Bug runtime/28958] New: " bill at broadley dot org
2022-03-11 19:08 ` [Bug runtime/28958] " bill at broadley dot org
2022-03-11 19:11 ` [Bug testsuite/28958] " bill at broadley dot org
2022-03-17 20:18 ` wcohen at redhat dot com
2022-03-17 21:49 ` bill at broadley dot org
2022-03-18 14:40 ` wcohen at redhat dot com
2022-03-18 15:18 ` wcohen at redhat dot com
2022-03-22 17:55 ` wcohen at redhat dot com
2022-03-25 18:22 ` bill at broadley dot org
2022-03-25 20:02 ` wcohen at redhat dot com [this message]
2022-03-25 22:27 ` bill at broadley dot org
2022-03-26 20:07 ` 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-28958-6586-KJJE0uhKSE@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).