From: "Dominic Jäger" <d.jaeger@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 2/2] pvecm: Add output for delnode
Date: Wed, 22 Jul 2020 12:20:52 +0200 [thread overview]
Message-ID: <20200722102052.25546-2-d.jaeger@proxmox.com> (raw)
In-Reply-To: <20200722102052.25546-1-d.jaeger@proxmox.com>
The output of "pvecm delnode someNode" is "Killing node X". Even though this
only says something about an attempt and not about success, it is not "no
output is returned".
Signed-off-by: Dominic Jäger <d.jaeger@proxmox.com>
---
pvecm.adoc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/pvecm.adoc b/pvecm.adoc
index 9207571..220c09f 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -327,11 +327,11 @@ After powering off the node hp4, we can safely remove it from the cluster.
----
hp1# pvecm delnode hp4
+ Killing node 4
----
-If the operation succeeds no output is returned, just check the node
-list again with `pvecm nodes` or `pvecm status`. You should see
-something like:
+Use `pvecm nodes` or `pvecm status` to check the node list again. It should
+look something like:
----
hp1# pvecm status
--
2.20.1
next prev parent reply other threads:[~2020-07-22 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 10:20 [pve-devel] [PATCH docs 1/2] pvecm: Add required -r to rm Dominic Jäger
2020-07-22 10:20 ` Dominic Jäger [this message]
2020-08-20 13:31 ` [pve-devel] applied: [PATCH docs 2/2] pvecm: Add output for delnode Thomas Lamprecht
2020-07-22 10:31 ` [pve-devel] [PATCH docs 1/2] pvecm: Add required -r to rm Thomas Lamprecht
2020-07-23 7:17 ` Dominic Jäger
2020-08-20 13:31 ` [pve-devel] applied: " 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=20200722102052.25546-2-d.jaeger@proxmox.com \
--to=d.jaeger@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