From: Alexander Aring <aahringo@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCHv2 dlm-tool 0/9] dlm-tool: pending fixes/cleanups dlm-tool patches
Date: Tue, 7 Mar 2023 12:12:58 -0500 [thread overview]
Message-ID: <20230307171307.2785162-1-aahringo@redhat.com> (raw)
Hi,
this is a resend of a subset of pending dlm-tool patches just without
the dlm_controld functionality to plot the dlm_controld posix cluster-wide
lock states over time. I split this feature out to have at first those
cleanups in fixes/dlm userspace instead of doing a new feature at the
same time now which has more things to dicuss about.
- Alex
Alexander Aring (9):
dlm_tool: add fail functionality if dump failed
dlm_controld: always create logdir
dlm_controld: move processing of saved messages to plock level
dlm_controld: remove ls parameter
dlm_controld: constify timeval of dt_usec()
dlm_controld: add gcc format printf attribute to log_level
dlm_controld: use write_result()
dlm_controld: be sure we stop lockspaces before shutdown
dlm_controld: constify name_in in log_level()
dlm_controld/daemon_cpg.c | 16 ++++++++--
dlm_controld/dlm_daemon.h | 3 +-
dlm_controld/lib.c | 25 +++++++++-------
dlm_controld/libdlmcontrol.h | 10 +++----
dlm_controld/logging.c | 36 +++++++++++------------
dlm_controld/plock.c | 25 ++++++++--------
dlm_tool/main.c | 57 +++++++++++++++++++++++++++---------
7 files changed, 108 insertions(+), 64 deletions(-)
--
2.31.1
next reply other threads:[~2023-03-07 17:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 17:12 Alexander Aring [this message]
2023-03-07 17:12 ` [Cluster-devel] [PATCHv2 dlm-tool 1/9] dlm_tool: add fail functionality if dump failed Alexander Aring
2023-03-07 17:13 ` [Cluster-devel] [PATCHv2 dlm-tool 2/9] dlm_controld: always create logdir Alexander Aring
2023-03-07 17:13 ` [Cluster-devel] [PATCHv2 dlm-tool 3/9] dlm_controld: move processing of saved messages to plock level Alexander Aring
2023-03-07 17:13 ` [Cluster-devel] [PATCHv2 dlm-tool 4/9] dlm_controld: remove ls parameter Alexander Aring
2023-03-07 17:13 ` [Cluster-devel] [PATCHv2 dlm-tool 5/9] dlm_controld: constify timeval of dt_usec() Alexander Aring
2023-03-07 17:13 ` [Cluster-devel] [PATCHv2 dlm-tool 6/9] dlm_controld: add gcc format printf attribute to log_level Alexander Aring
2023-03-07 17:13 ` [Cluster-devel] [PATCHv2 dlm-tool 7/9] dlm_controld: use write_result() Alexander Aring
2023-03-07 17:13 ` [Cluster-devel] [PATCHv2 dlm-tool 8/9] dlm_controld: be sure we stop lockspaces before shutdown Alexander Aring
2023-03-07 17:13 ` [Cluster-devel] [PATCHv2 dlm-tool 9/9] dlm_controld: constify name_in in log_level() Alexander Aring
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=20230307171307.2785162-1-aahringo@redhat.com \
--to=aahringo@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 NNTP newsgroup(s).