DOBASHRC=false does not prevent .bashrc from being updated

Install, Configure and Update
1

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:

Screenshot 2025-07-06 at 4.13.37 PM
Screenshot 2025-07-06 at 4.13.37 PM964×276 75.3 KB

A fix for this would be useful as it makes shared home directories more cumbersome.

2

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…?

3

@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
4

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).

5

Thanks @UCBKurt @rbs_sci for reporting your observations.
@UCBKurt Please can you provide more details:

  1. What is the CryoSPARC version to whose install.sh and DOBASHRC variable you referred?
  2. Is the storage for the /raid/0/cryosparc path shared between nodes?
  3. 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?
6

  1. v4.7.1-cuda12

  2. No, it is local nvme storage on each node

  3. 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.

7

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?

8

In short succession.

9

@wtempel Any update on this? It’s starting to get out of hand a bit.

Screenshot 2025-07-09 at 9.38.24 AM
Screenshot 2025-07-09 at 9.38.24 AM1532×1530 232 KB

10

@UCBKurt Currently, repetitive export PATH= statements could be added added automatically to ~/.bashrc if

  1. install.sh is run with the --yes option
  2. 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