From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 2/2] ha-manager: move hardware watchdog out of the requirements list
Date: Wed, 21 May 2025 16:03:43 +0200 [thread overview]
Message-ID: <20250521140343.366871-3-m.sandoval@proxmox.com> (raw)
In-Reply-To: <20250521140343.366871-1-m.sandoval@proxmox.com>
Having a hardware watchdog is not a requirement, we move it out of the
list so it is not as prominent.
Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
---
ha-manager.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/ha-manager.adoc b/ha-manager.adoc
index 7f7f0bb..5fdd5cf 100644
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -118,8 +118,8 @@ You must meet the following requirements before you start with HA:
* use reliable “server” components
-* hardware watchdog - if not available we fall back to the
- linux kernel software watchdog (`softdog`)
+Optionally, a hardware watchdog can be used - if not available we fall back to
+the linux kernel software watchdog (`softdog`).
[[ha_manager_resources]]
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-05-21 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 14:03 [pve-devel] [PATCH docs 0/2] ha-manager: simplify requirements Maximiliano Sandoval
2025-05-21 14:03 ` [pve-devel] [PATCH docs 1/2] ha-manager: remove hardware fencing from requirements Maximiliano Sandoval
2025-07-16 23:09 ` [pve-devel] applied: " Thomas Lamprecht
2025-05-21 14:03 ` Maximiliano Sandoval [this message]
2025-07-16 23:09 ` [pve-devel] applied: [PATCH docs 2/2] ha-manager: move hardware watchdog out of the requirements list 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=20250521140343.366871-3-m.sandoval@proxmox.com \
--to=m.sandoval@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 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.