Title says it all. Looking at the install.sh, exporting DOBASHRC=false
should result in the user’s ~/.bashrc
file not being updated with the cryosparcm
path.
Instead, you get this after multiple installs with a shared home directory:
A fix for this would be useful as it makes shared home directories more cumbersome.
The inverse problem exists if using ZSH as the default shell - CryoSPARC asks to add, but doesn’t! To either .zshrc
or .bashrc
.
Although the increased risks of malware propagation, accidental information dissemination and social engineering attacks that come with a shared /home
directory seems like it would make any CISO freak out…?
@rbs_sci shared home directories across nodes are normal in HPC environments. A user’s $HOME
is usually on a shared filesystem across all nodes.
1 Like
Righto. I guess I misunderstood what you meant by shared /home
? (I understood it to mean multiple users logging in to the same /home/[user]
, not remotely mounted /home
folders available to multiple nodes).
Thanks @UCBKurt @rbs_sci for reporting your observations.
@UCBKurt Please can you provide more details:
- What is the CryoSPARC version to whose
install.sh
and DOBASHRC
variable you referred?
- Is the storage for the
/raid/0/cryosparc
path shared between nodes?
- Do you know how long each of the
export PATH=
lines has been present in your ~/.bashrc
file? Could they all have arisen from installations of older CryoSPARC versions?
-
v4.7.1-cuda12
-
No, it is local nvme storage on each node
-
They’ve only appeared since I started installing v4.7.1-cuda12 on Wednesday.
Right now, I’m having to run a sed
command to check and delete those lines, so being able to use DOBASHRC=false
would be useful.
Thanks for the information @UCBKurt.
Does this mean that you freshly installed CryoSPARC v4.7.1-cuda12 on four (or more?) nodes simultaneously or in short succession?
@wtempel Any update on this? It’s starting to get out of hand a bit.
@UCBKurt Currently, repetitive export PATH=
statements could be added added automatically to ~/.bashrc
if
install.sh
is run with the --yes
option
- and
install.sh --yes
is run again in association with a shared .bashrc
without first loading the already updated ~/.bashrc
Could this have happened in your case?
the DOBASH
variable is not designed for assignment by the user, and setting DOBASH=false
is not expected to prevent repetitive addition of export PATH=
statements to ~/.bashrc
under the hypothetical scenario above. Thanks for reporting this observation! We are looking into addressing the issue in a future release.
@rbs_sci We made a note about your interest in support for ZSH configuration.
1 Like