Re: [pve-devel] [PATCH docs 1/2] ssh: make pitfalls a regular section instead of block

Re: [pve-devel] [PATCH docs 1/2] ssh: make pitfalls a regular section instead of block

[Fiona Ebner]

Am 12.01.24 um 13:40 schrieb Esi Y:
>> @@ -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?
> 
>

Yes, that is too radical and unexpected. Users will not be happy if
their .bashrc is automatically overwritten. It's perfectly legitimate to
log in as root for an admin and use bash, so forcing something upon
people there is not nice.

(Sorry, CC for the mailing list got lost, so re-sending)

[pve-devel] [PATCH docs 1/2] ssh: make pitfalls a regular section instead of block

[Fabian Grünbichler]

because we'll add another one before it, and formatting is off otherwise.

Signed-off-by: Fabian Grünbichler <f.gruenbichler@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
 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