Differences

This shows you the differences between two versions of the page.

--- services:modules [2019/07/25 13:51]
giunta [Controlling Modules During Login]
+++ services:modules [2019/07/25 14:34] (current)
giunta [Tips for graphical login]
@@ Line 73: / Line 73: @@
 This will search any help message or whatis description for the word(s) given on the command line.
-Another way to search for modules is with the ''module spider''command. This command searches the entire list of possible modules. The difference between ''module avail'' and ''module spider'' is explained in the [[services:modules#module_hierarchy|Module Hierarchy]] and [[services:modules#searching_for_modules|Searching for Modules]] section.:
+Another way to search for modules is with the ''module spider''command. This command searches the entire list of possible modules. The difference between ''module avail'' and ''module spider'' is explained in the [[services:modules#module_hierarchy|Module Hierarchy]] and [[services:modules#searching_for_modules|Searching for Modules]] section:
   $ module spider
@@ Line 219: / Line 219: @@
 endif
 </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 workstations, //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 =====