Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
services:modules [2019/07/25 13:53] giunta [Usage] |
services:modules [2019/07/25 14:32] giunta [Tips for graphical login] |
||
|---|---|---|---|
| Line 219: | Line 219: | ||
| endif | endif | ||
| </code> | </code> | ||
| + | |||
| + | ==== Tips for graphical login ==== | ||
| + | |||
| + | When using automatically loaded modules, a possible solution to avoid problems on GNOME login could be testing ''TERM'' environment variable. In this way, only when users open a graphical terminal (e.g., GNOME Terminal), modules will be loaded. On SISSA linux workstation, //GNOME Terminal// sets it as ''xterm-256color''. Bash users may add a test on ''TERM'' variable in their ''~/.bashrc'': | ||
| + | |||
| + | <code> | ||
| + | if [ "$TERM" == "xterm-256color" -a -z "$BASHRC_READ" ]; then | ||
| + | export BASHRC_READ=1 | ||
| + | # Place any module commands here | ||
| + | # module load git | ||
| + | fi | ||
| + | </code> | ||
| + | |||
| + | Csh users need to add in their ''~/.cshrc'' file: | ||
| + | |||
| + | <code> | ||
| + | if ( "$TERM" == "xterm-256color" && ! $?CSHRC_READ ) then | ||
| + | setenv CSHRC_READ 1 | ||
| + | # Place any module command here | ||
| + | # module load git | ||
| + | endif | ||
| + | </code> | ||
| + | |||
| ===== User Collections ===== | ===== User Collections ===== | ||