From: Oguz Bektas <o.bektas@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs] pvecm: document modified .bashrc case for ssh
Date: Thu, 12 Nov 2020 17:39:44 +0100 [thread overview]
Message-ID: <20201112163944.1754863-1-o.bektas@proxmox.com> (raw)
use the snippet from /etc/skel/.bashrc for checking
if session is interactive, if non-interactive return
and do nothing.
Signed-off-by: Oguz Bektas <o.bektas@proxmox.com>
---
pvecm.adoc | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/pvecm.adoc b/pvecm.adoc
index 3820c17..f7abfcd 100644
--- a/pvecm.adoc
+++ b/pvecm.adoc
@@ -171,6 +171,19 @@ since guest IDs could be conflicting. As a workaround create a backup of the
guest (`vzdump`) and restore it as a different ID after the node has been added
to the cluster.
+IMPORTANT: SSH is used for inter-node communications through tunneling. If you
+have a custom `.bashrc` or similar file, this would get executed during some API
+calls. To avoid such complications, you can add the following snippet to `/root/.bashrc`
+at the beginning of the file:
+
+----
+# If not running interactively, don't do anything
+case $- in
+ *i*) ;;
+ *) return;;
+esac
+----
+
Join Node to Cluster via GUI
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
2.20.1
reply other threads:[~2020-11-12 16:39 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=20201112163944.1754863-1-o.bektas@proxmox.com \
--to=o.bektas@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.