public:lle

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revisionBoth sides next revision
public:lle [2009-09-29 14:55] Arno Schoenmakerspublic:lle [2017-05-30 10:47] – [Login scripts] Arno Schoenmakers
Line 1: Line 1:
 ====== The Lofar Login Environment (LLE) ====== ====== The Lofar Login Environment (LLE) ======
  
-This page describes the standard login environment for new users on the LOFAR cluster nodes. It can also be applied to accounts at the WRST site and on the Dwingeloo Linux systems. +This page describes the standard login environment for new users on the LOFAR cluster nodes like [[cep3:start|CEP3]]
 Existing accounts can be easily modified; see below for a manual to do this. Existing accounts can be easily modified; see below for a manual to do this.
  
Line 16: Line 15:
 ===== What to do when you get an account ===== ===== What to do when you get an account =====
  
-==== (t)csh ==== +The CEP3 user creation system has been setup such that new accounts will have all needed files and links in ''$HOME'' in place alreadySo you do not have to chnage anything to work with the LLE.
- +
-If you have chosen for the ''(t)csh'' shell, you do as follows: +
-  * Log in and go to your (empty) ''$HOME'' directory +
-  * ''> ln -s /opt/login/cshrc .cshrc'' (Note: on lioffen you should refer to ''/app/login/cshrc'' !) +
-  * Log out and login again; you should see a welcome message. +
- +
-==== bash ==== +
- +
-If you have chosen for the ''bash'' shell, you do as follows: +
-  * Log in and go to your (empty) ''$HOME'' directory +
-  * ''> ln -s /opt/login/bashrc .bashrc'' (Note: on lioffen you should refer to ''/app/login/cshrc'' !) +
-  * Log out and login again; you should see a welcome message. +
  
 ===== How to transform existing accounts? ===== ===== How to transform existing accounts? =====
  
-To use the LLE in an existing account, rename your existing ''.cshrc'' or ''.bashrc'' in your ''$HOME'' and follow the instructions given above. +To use the LLE in an existing account and ''$HOME'' dir, rename your existing ''.cshrc''or ''.profile'' and ''.bashrc''in your ''$HOME'' and follow the instructions given above.
- +
-Make sure that possibly existing files ''$HOME/.login'', ''$HOME/.setenv'' and ''$HOME/.alias'' that you still want to use at login time are renamed to ''$HOME/.mylogin'', ''$HOME/.mysetenv'', ''$HOME/.myalias''+
- +
- +
  
 ===== The LLE scripts ===== ===== The LLE scripts =====
  
 Some of the details are presented here. Some of the details are presented here.
- 
-==== What is $APS_LOCAL ? ==== 
- 
-The root directory for the scripts is provided in environment variable ''$APS_LOCAL'', whose value is set in the ''.cshrc'' and ''.bashrc'' scripts. The actual value depends on your location: 
-  * New CEP processing cluster: ''/opt'' 
-  * lioffen and its nodes: ''/app'' 
  
  
 ==== Login scripts ==== ==== Login scripts ====
  
-In directory ''${APS_LOCAL}/login'' are a number of default login scripts. The scripts ending with ''.bash'' are for the ''bash'' shell, the others for the ''(t)csh'' shell: \\ +In directory ''/opt/cep/login'' are a number of default login scripts. The scripts ending with ''.bash'' are for the ''bash'' shell, the others for the ''(t)csh'' shell: \\ 
-  * ''cshrc'' -> sets APS_LOCAL and calls the other scripts +  * ''cshrc'' -> login settings for (t)csh environments. 
-  * ''login'' -> Displays welcome message; no settings +  * ''bashrc'' -> login settings for non-interactive logins. 
-  * ''setenv'' -> adds some items to $PATH, sets your prompt, etc+  * ''profile'' -> login settings for interactive logins
-  * ''alias'' -> some default aliases to make life easy +  * ''login'' -> Displays welcome message; no settings. 
-  * ''setpackages'' -> script to define packages to initialize at login-time+  * ''setpackages'' -> script to define packages to initialize at login-time.
 \\ \\
  
-Users should **NEVER** modify these default scripts at this location! +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 ====
  
-Personal command aliases can be added to a file ''$HOME/.myalias''. When this file exists, the ''.cshrc'' or ''.bashrc'' script will read this file after reading the default ''${APS_LOCAL}/login/alias(.bash)''.+Personal command aliases can be added to a file ''$HOME/.myalias''. When this file exists, the ''.cshrc'' or ''.bashrc'' script will read this file.
  
 ==== Personal environment settings: .mysetenv ==== ==== Personal environment settings: .mysetenv ====
Line 74: Line 49:
  
  
-===== Package initialisation: .mypackages =====+===== Package initialisation =====
  
-To initialize the use of installed packages on your system you must create a file ''$HOME/.mypackages''. If this file existsit is used by the LLE script ''setpackages''.+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]]).
  
-In the directory ''${APS_LOCAL}/scripts'' you will find available package initialization scripts, named like ''do<package>'' (e.g., ''doCasacore'', ''doPyrap''). Whenever you add a package to the file ''$HOME/.mypackages'', the associated script in ''$APS_LOCAL/scripts'' will be ''source'''d.+==== .mypackages =====
  
-The file ''$HOME/.mypackages'' can look like this:+To initialize the use of installed packages at login time you must create a file ''$HOME/.mypackages''. If this file exists, it is used by the LLE script ''setpackages''
 + 
 +The file ''$HOME/.mypackages'' can look like this example:
 <code> <code>
-Casacore +casa 
-doPyrap+lofim
 </code> </code>
  
-The packages can be on one line or on multiple linesAlso note the use of ''<package>'' and ''do<package>''; both are accepted. If an initialization script cannot be found, it will be reported to the user. +Provide only one package name per line.  
 +For packages that are build daily and that have a version available for all days of the week (LUS, LofIm), you can also specify a day of week in the ''.mypackages'' file: 
 +<code
 +lofim Tue 
 +</code>
  
 ==== How to add a personal package ==== ==== How to add a personal package ====
  
-Apart from the systemwide ''do<package>'' files provided in directory ''$APS_LOCAL/scripts'', users can add their personal ''do<package>'' files in their ''$HOME'' and have these run at login time. If there is a ''do<package>'' file both in $HOME and in ''$APS_LOCAL/scripts'', the version in ''$HOME'' has preference and will be executed. This can be used to test a different version of a package, etc... To add a new, personal, package, 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/do<package>'' initialization script (e.g., adding the installation directory to your ''$PATH'')+  * 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''
- 
- 
- 
- 
- 
- 
  
 ===== Starting X environment ===== ===== Starting X environment =====
Line 112: Line 86:
 This should start your X environment at the proper colordepth. This should start your X environment at the proper colordepth.
 This will create an additional X Server next to the one you are already running. You can access this with Alt-F8 or Cntl-Alt-F8. The F7 variant will give you back your normal X. This will create an additional X Server next to the one you are already running. You can access this with Alt-F8 or Cntl-Alt-F8. The F7 variant will give you back your normal X.
 +
 +Due to the large latency and largte bandwidth required for X-traffic, it is advisable to connect to the CEP systems with the ''NX''-client on your system. See [[public:freenx-windows-client|this page for more info]]. 
  
 ===== Help! ===== ===== Help! =====
  
-If you need help, or have questions, or want to give any other comments, contact Arno Schoenmakers or Adriaan Renting.+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 is available systemwide. Contact Arno Schoenmakers or Adriaan Renting 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.
  
  • Last modified: 2020-11-04 15:49
  • by Bernard Asabere