[pve-devel] [PATCH docs 1/2] ssh: make pitfalls a regular section instead of block
Esi Y
esiy0676+proxmox at gmail.com
Fri Jan 12 13:40:25 CET 2024
On Thu, Jan 11, 2024 at 11:51:19AM +0100, Fabian Grünbichler wrote:
> because we'll add another one before it, and formatting is off otherwise.
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler at proxmox.com>
> ---
> pvecm.adoc | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/pvecm.adoc b/pvecm.adoc
> index 1f78585..5b5b27b 100644
> --- a/pvecm.adoc
> +++ b/pvecm.adoc
> @@ -918,9 +918,9 @@ transfer memory and disk contents.
>
> * Storage replication
>
> -.Pitfalls due to automatic execution of `.bashrc` and siblings
> -[IMPORTANT]
> -====
> +Pitfalls due to automatic execution of `.bashrc` and siblings
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> In case you have a custom `.bashrc`, or similar files that get executed on
Would it be too radical to suggest that PVE as an appliance could afford to overwrite .bashrc upon every boot for the root account and document that instead? The other alternative is to use different user for PVE tasks, but why have/allow custom .bashrc on a root to begin with?
> login by the configured shell, `ssh` will automatically run it once the session
> is established successfully. This can cause some unexpected behavior, as those
> @@ -940,8 +940,6 @@ case $- in
> *) return;;
> esac
> ----
> -====
> -
>
> Corosync External Vote Support
> ------------------------------
> --
> 2.39.2
>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel at lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
More information about the pve-devel
mailing list