From: Steve Dickson <steved@redhat.com>
To: Bill Baker <webbaker@gmail.com>, Calum Mackay <calum.mackay@oracle.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/5] Flight Data Recorder Update
Date: Sun, 30 Jan 2022 14:06:06 -0500 [thread overview]
Message-ID: <20220130190611.12292-1-steved@redhat.com> (raw)
Here a few updates to the FDR package that
will allow it to work out of the box when
the RPM is install... Kinda.
When the rpm is installed, the daemon is not enable or
started and the config file is not enabled. But it
makes much easier set a tracepoint. Uncomment
the needed tracepoint and start the fdrd daemon.
Then do tail -f on /var/log/nfs.log.
The package is very light weight: one daemon, two config
files and one example file. The config file that is installed
has all of the nfs,nfsv4 and sunrpc tracepoints, commented
out.
The first 4 patches are clean up... Making things work
right out of the box and conforming to current
presidencies. The last patch, installing an nfsall.conf
config, could be questionable. Do the maintainers want
to maintain config files or have the distros do it?
I guess the bottom line is this. At the last bakeathon
we talked about moving away from rpcdebug setting
dprintks to tracepoints (which is a good thing IMHO).
Now, it is not clear how it can be done, but I'm
hoping this is the first step in that direction.
Steve Dickson (5):
Makefile: cleaned up the usage of RPMBUILD_DIR
fdr.spec: logrotate clean up
systemd: rename service file.
saveto verb: Document updated
configs: Add an nfsall.conf config file
Makefile | 8 +-
buildrpm/1.3/fdr.spec | 25 ++-
configs/nfsall.conf | 319 ++++++++++++++++++++++++++++++++++++
fdrd.man | 9 +-
fdr.service => fdrd.service | 0
samples/nfs | 2 +
6 files changed, 349 insertions(+), 14 deletions(-)
create mode 100644 configs/nfsall.conf
rename fdr.service => fdrd.service (100%)
--
2.34.1
next reply other threads:[~2022-01-30 19:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 19:06 Steve Dickson [this message]
2022-01-30 19:06 ` [PATCH 1/5] Makefile: cleaned up the usage of RPMBUILD_DIR Steve Dickson
2022-01-30 19:06 ` [PATCH 2/5] fdr.spec: logrotate clean up Steve Dickson
2022-01-30 19:06 ` [PATCH 3/5] systemd: rename service file Steve Dickson
2022-01-30 19:06 ` [PATCH 4/5] saveto verb: Document updated Steve Dickson
2022-01-30 19:06 ` [PATCH 5/5] configs: Add an nfsall.conf config file Steve Dickson
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=20220130190611.12292-1-steved@redhat.com \
--to=steved@redhat.com \
--cc=calum.mackay@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=webbaker@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.