| Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision |
| public:lle [2017-05-24 14:50] – [Login scripts] Arno Schoenmakers | public:lle [2017-05-30 10:47] – [Login scripts] Arno Schoenmakers |
|---|
| \\ | \\ |
| |
| Users should **NEVER** modify these default scripts. In their $HOME these should be symlinks to the versions in ''/opt/cep/login''. Personalization of your login is possible through other scripts like ''.myalias'' and ''.mysetenv'' (see below). | Users should **NEVER** modify these default scripts. In their ''$HOME'' these should be symlinks to the versions in ''/opt/cep/login''. Personalization of your login is possible through other scripts like ''.myalias'' and ''.mysetenv'' (see below). |
| |
| |
| | If you like to read more on the files that play a role in the bash login, [[https://stackoverflow.com/questions/415403/whats-the-difference-between-bashrc-bash-profile-and-environment|here is a nice link]]. |
| ==== Personal command aliasses: .myalias ==== | ==== Personal command aliasses: .myalias ==== |
| |
| ===== Package initialisation ===== | ===== Package initialisation ===== |
| |
| Many packages are available from the distribution of the Operating System. Several packages are added lateron, see [[cep3:usersoftware|this page for CEP3 packages]]. To activate these, environment variables like ''PATH'', ''LD_LIBRARY_PATH'', ''PYTHONPATH'' must be set correctly. To help you, we have installed the environment module software (see [[cep3:usersoftware#using_packages_with_environment_modules|this section in the CEP3 user documentation]]. | Many packages are available from the distribution of the Operating System. Several packages are added lateron, see [[cep3:usersoftware|this page for CEP3 packages]]. To activate these, environment variables like ''PATH'', ''LD_LIBRARY_PATH'', ''PYTHONPATH'' must be set correctly. To help you, we have installed the environment module software (see [[cep3:usersoftware#using_packages_with_environment_modules|this section in the CEP3 user documentation]]). |
| |
| ==== .mypackages ===== | ==== .mypackages ===== |
| Apart from the systemwide module initialization files provided in directory ''$APS_LOCAL/modulefiles'', users can add their personal modulefiles in their ''$HOME/modulefiles'' and have these run at login time. To add a new, personal, modulefile, act as follows: | Apart from the systemwide module initialization files provided in directory ''$APS_LOCAL/modulefiles'', users can add their personal modulefiles in their ''$HOME/modulefiles'' and have these run at login time. To add a new, personal, modulefile, act as follows: |
| * Install the package | * Install the package |
| * Create a ''$HOME/modulefiles/<package>/<modulefile>'' environment module script (e.g., adding the installation directory to your ''$PATH''). See [[http://modules.sourceforge.net/man/modulefile.html|this manula for writing modulefiles yourself]]. | * Create a ''$HOME/modulefiles/<package>/<modulefile>'' environment module script (e.g., adding the installation directory to your ''$PATH''). See [[http://modules.sourceforge.net/man/modulefile.html|this manual for writing modulefiles yourself]]. |
| * Add <package> to the list of packages in file ''$HOME/.mypackages'' | * Add <package> to the list of packages in file ''$HOME/.mypackages'' |
| |
| If you need help, or have questions, or want to give any other comments, contact Arno Schoenmakers or Reinoud Bokhorst. | If you need help, or have questions, or want to give any other comments, contact Arno Schoenmakers or Reinoud Bokhorst. |
| |
| New ''do<xxxx>''-files can be added at any time if you have a new package that should be available systemwide. Contact Arno Schoenmakers or Reinoud Bokhorst in this case. | New module-files can be added at any time if you have a new package that should be available systemwide. Contact Arno Schoenmakers or Reinoud Bokhorst in this case. |
| |