From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] qdevice: remove outdated reference to qnetd package
Date: Thu, 2 Mar 2023 09:48:33 +0100 [thread overview]
Message-ID: <20230302084833.862843-1-f.gruenbichler@proxmox.com> (raw)
we provided the package back in the Stretch/Buster based releases, but don't
anymore since the package in Debian is recent enough nowadays.
Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
---
Notes:
reported on the forum: https://forum.proxmox.com/threads/question-regarding-corosync-qnetd-package.123540/
pvecm.adoc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/pvecm.adoc b/pvecm.adoc
index 446735c..81f770d 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -980,9 +980,9 @@ state free. New clusters are handled dynamically and no configuration file
is needed on the host running a QDevice.
The only requirements for the external host are that it needs network access to
-the cluster and to have a corosync-qnetd package available. We provide a package
-for Debian based hosts, and other Linux distributions should also have a package
-available through their respective package manager.
+the cluster and to have a corosync-qnetd package available in a compatible
+version. Most current Linux distributions should have a package available
+through their respective package manager.
NOTE: Unlike corosync itself, a QDevice connects to the cluster over TCP/IP.
The daemon can also run outside the LAN of the cluster and isn't limited to the
--
2.30.2
reply other threads:[~2023-03-02 8:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230302084833.862843-1-f.gruenbichler@proxmox.com \
--to=f.gruenbichler@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