You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When invoked as an interactive login shell, Bash looks for the /etc/profile file, and if the file exists, it runs the commands listed in the file. Then Bash searches for ~/.bash_profile, ~/.bash_login, and ~/.profile files, in the listed order, and executes commands from the first readable file found.
When Bash is invoked as an interactive non-login shell, it reads and executes commands from ~/.bashrc, if that file exists, and it is readable.
So as the NCSA team
... have prepared a hal-login3 machine as a login node so that users can request computational resources from hal-dgx and overdrive.
then when an interactive session on HAL DGX is requested it will not be a login shell and so ~/.bash_profile will never be sourced.
The solution then is to move all the components that were in ~.bash_profile into ~/.basrc_user. So this will require rewrites of migrate_home.sh and pyenv_setup.sh.
The text was updated successfully, but these errors were encountered:
After the NCSA team setup a login node for the HAL DGX box (c.f. Access hal-dgx and overdrive with hal-login3 Node) the
.bash_profile
based setup workflow failed asSo as the NCSA team
then when an interactive session on HAL DGX is requested it will not be a login shell and so
~/.bash_profile
will never be sourced.The solution then is to move all the components that were in
~.bash_profile
into~/.basrc_user
. So this will require rewrites ofmigrate_home.sh
andpyenv_setup.sh
.The text was updated successfully, but these errors were encountered: