abstract:farber:app_dev:compute_env

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
abstract:farber:app_dev:compute_env [2018-05-23 11:44] – [UNIX shell] anitaabstract:farber:app_dev:compute_env [2021-04-27 16:20] (current) – [Startup and logout scripts] anita
Line 1: Line 1:
 ====== Computing Environment ====== ====== Computing Environment ======
-//The following sections use the wiki's [[:#documentation-conventions|documentation conventions]].//+
  
 ===== UNIX shell ===== ===== UNIX shell =====
Line 7: Line 7:
  
 For most Linux systems, the //sh// shell is the //bash// shell and the //csh// shell is the //tcsh// shell. The remainder of this document will use only // bash// commands. For most Linux systems, the //sh// shell is the //bash// shell and the //csh// shell is the //tcsh// shell. The remainder of this document will use only // bash// commands.
 +
 +== ==
 +//The following sections use the wiki's [[:#documentation-conventions|documentation conventions]].//
  
 ===== Environment variables ===== ===== Environment variables =====
Line 55: Line 58:
  
 <code bash> <code bash>
-    cp /etc/skel/.bash* $HOME+    cp /opt/shared/templates/homedir/.bash* $HOME
 </code> </code>
 <note tip>**Where to put startup commands:** You can put bash commands in either ''~/.bashrc'' or ''~/.bash_profile''.  Here are general suggestions: <note tip>**Where to put startup commands:** You can put bash commands in either ''~/.bashrc'' or ''~/.bash_profile''.  Here are general suggestions:
Line 107: Line 110:
 <note tip>Use ''$WORKDIR'' when you refer to your group private directory.  This will improve portability. </note> <note tip>Use ''$WORKDIR'' when you refer to your group private directory.  This will improve portability. </note>
 <note tip> <note tip>
-It is always important to be aware of your current workgroup name.  The standard prompt includes the workgroup name, added to your username and host.  You must have a workgroup name in your prompt to use that cluster group's (//investing-entity//) compute nodes to submit jobs using [[abstract:farber:runapps?s[]=submit&s[]=job#submitting-jobs-qsub|qsub]] or qlogin. An example prompt after the **workgroup** command,+It is always important to be aware of your current workgroup name.  The standard prompt includes the workgroup name, added to your username and host.  You must have a workgroup name in your prompt to use that cluster group's (//investing-entity//) compute nodes to submit jobs using [[:abstract:farber:runjobs:schedule_jobs#batch-jobs-qsub|qsub]] or [[:abstract:farber:runjobs:schedule_jobs#interactive-jobs-qlogin|qlogin]]. An example prompt after the **workgroup** command,
  
 ''[(it_css:traine)@farber ~]$ '' ''[(it_css:traine)@farber ~]$ ''
Line 137: Line 140:
 It is always important to be aware of your current working directory.  The standard prompt ends with the basename of ''PWD''.  In these two examples the basename is the same, ''traine'', but the standard bash ''PROMPT_COMMAND'', which is executed every time you change directories, will put the full path of your current working directory in your window title. For example, It is always important to be aware of your current working directory.  The standard prompt ends with the basename of ''PWD''.  In these two examples the basename is the same, ''traine'', but the standard bash ''PROMPT_COMMAND'', which is executed every time you change directories, will put the full path of your current working directory in your window title. For example,
  
-''traine@farber:/lustre/work/it_css/users/traine''+''traine@farber:/home/work/it_css/users/traine''
 </note> </note>
  
  • abstract/farber/app_dev/compute_env.1527090293.txt.gz
  • Last modified: 2018-05-23 11:44
  • by anita