We’ll assume here that you’re using nano.įrom a login or other node on the cluster, type nano ~/.bashrc to open the file in the nano editor. You may also be able to edit the file using your SFTP client of choice, but experiences may vary. bashrc, you’ll need to be comfortable with a command-line editor such as nano (probably the easiest to get started with) or vim (aka vi). On Odysse圓 you can leave or remove is as it’s benign after the CentOS 7 upgrade. If you see source new-modules.sh, that’s what that is. bashrc may contain the Odyssey2 module definitions call there. Please do not remove this section as you will run into problems as a result.įor instance, your. The /etc/bashrc file includes definitions necessary to make your jobs and other interactions run properly across the cluster. bashrc as that will cause them to run after the global definitions have been sourced.The # Source global definitions section is where the default Odyssey-wide definitions are sourced. bashrcĪfter the # User specific aliases and functions section is where you should put any customizations of your. bashrc for you so you’re able to log in again. If that should happen, contact us and we can copy in a default.
Any time a new shell is created by your user, this file is sourced.Īs you might imagine, you need to be very careful not to break your. This runtime configuration file is processed (or ‘sourced’) by bash, the default shell on Odyssey, when you log into a node and by your jobs when they run.
If you always load the same module when logging in, or want to add other definitions for your login shell to process, that means editing the. There may come a time when you want to customize your default login environment.
0 kommentar(er)
