From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 1/3] pvecm: fix qnetd typo
Date: Mon, 20 Nov 2023 16:48:28 +0100 [thread overview]
Message-ID: <20231120154830.2640139-1-a.lauterer@proxmox.com> (raw)
Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
---
pvecm.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pvecm.adoc b/pvecm.adoc
index d595ac5..1f78585 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -1090,7 +1090,7 @@ The status output of the QDevice, as seen above, will usually contain three
columns:
* `A` / `NA`: Alive or Not Alive. Indicates if the communication to the external
- `corosync-qndetd` daemon works.
+ `corosync-qnetd` daemon works.
* `V` / `NV`: If the QDevice will cast a vote for the node. In a split-brain
situation, where the corosync connection between the nodes is down, but they
both can still communicate with the external `corosync-qnetd` daemon,
--
2.39.2
next reply other threads:[~2023-11-20 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 15:48 Aaron Lauterer [this message]
2023-11-20 15:48 ` [pve-devel] [PATCH docs 2/3] pveceph: fix typo Aaron Lauterer
2023-11-20 15:48 ` [pve-devel] [PATCH docs 3/3] pvecm: expand on public/cluster networks Aaron Lauterer
2023-11-20 16:01 ` [pve-devel] applied: [PATCH docs 1/3] pvecm: fix qnetd typo Thomas Lamprecht
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=20231120154830.2640139-1-a.lauterer@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.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