Difference between revisions of "Setting permanent default for software stack upon login"
From ScientificComputing
| Line 1: | Line 1: | ||
| − | |||
==Introduction== | ==Introduction== | ||
Some time ago we introduced a [[New_SPACK_software_stack_on_Euler|new software stack]] on Euler that uses a different, but similar, module system (LMOD modules instead of environment modules) which has useful additional features on top of what environment modules provide. | Some time ago we introduced a [[New_SPACK_software_stack_on_Euler|new software stack]] on Euler that uses a different, but similar, module system (LMOD modules instead of environment modules) which has useful additional features on top of what environment modules provide. | ||
| Line 9: | Line 8: | ||
* Users of the new software stack could add the command | * Users of the new software stack could add the command | ||
source /cluster/apps/local/env2lmod.sh | source /cluster/apps/local/env2lmod.sh | ||
| − | to their .bashrc | + | to their .bashrc |
| − | |||
Revision as of 07:42, 11 January 2021
Introduction
Some time ago we introduced a new software stack on Euler that uses a different, but similar, module system (LMOD modules instead of environment modules) which has useful additional features on top of what environment modules provide.
So far upon login to the Euler cluster, the old software stack is initialized as the default and we provided the scripts env2lmod and lmod2env to switch between the old and the new software stack.
Having the old software stack initialized upon login causes some issues for users of the new software stack
- Users of the new software stack could add the command
source /cluster/apps/local/env2lmod.sh
to their .bashrc
