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 mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
