This page describes the different variables used by the HEPiX Shell Scripts. They can be roughly classified into
Index: BINTYPE - CLUSTER_DIR - DOMAINNAME - EDITOR - FCEDIT - FPATH - GROUP - GROUP_DIR - GROUPMANPATH - GROUPPATH - HOST - INITIALE - INITIALISED - LD_LIBRARY_PATH - LESSCHARSET - MAIL - MAILBOX - MAILSERVER - MANPATH - NNTPSERVER - ORACLE* - OS - PAGER - PATH - RFASSIGN - ROOTPATH - RUBOUT - SYSMAN - SYSPATH - SYSTYPE - USER - USERPATH - VISUAL - WWW_HOME - X11BIN - XFILESEARCHPATH - YP
BINTYPE
Description:
Binary compatibility for executables
setting should reflect the binary compatibility for executables.
A supplied script called bintype will evaluate the bintype
automatically.
You can specify different levels for the evaluation.
Setting Policy:
This variable is usually set by the HEP or the Site level.
Scope:
This variable should be present in the user environment.
Example:
BINTYPE="AIX"
CLUSTER_DIR
Description:
The path to the Cluster cutomisation level.
Setting Policy:
This variable is set by the HEP or the Site level.
Scope:
This variable should be present in the user environment.
Example:
CLUSTER_DIR="/etc/hepix/cluster"
DOMAINNAME
Description:
Gives the name of the domain if NIS is enabled otherwise it is empty.
Setting Policy:
This variable is only set by the HEP or the Site level. Then it should
be unset in the environment part at HEP or Site level.
Scope:
This variable should NOT be present in the user environment.
Example:
DOMAINNAME=`domainname`
EDITOR
Description:
The default editor.
Setting Policy:
This variable can be set by any level.
Scope:
This variable should be present in the user environment.
Example:
EDITOR="pico -w"
FCEDIT
Description:
emacs for ksh.
Setting Policy:
This variable can be set by any level.
Scope:
This variable should be present in the user environment.
Example:
FCEDIT="emacs"
FPATH
Description:
/usr/local/lib/functions for zsh.
Setting Policy:
This variable can be set by any level.
Scope:
This variable should be present in the user environment.
Example:
FPATH="/usr/local/lib/functions"
GROUP
Description:
primary groupname
The primary UNIX group name of the user.
Setting Policy:
This variable should only be set by the HEP level.
Scope:
This variable MUST be present in the user environment.
Example:
GROUP="c3"
GROUP_DIR
Description:
The path where are stored the Group customisation level.
The location of the group level customisations. It is normally set
by the HEPiX shells scripts but used by the HEPiX X11 scripts by
default. If the HEPiX shells scripts are not used, it can be set at
site level in the %xprofile file.
Setting Policy:
This variable should only be set by the HEP and Site level.
Scope:
This variable should be present in the user environment.
Example:
GROUP_DIR="/afs/cern.ch/group/$GROUP"
GROUPMANPATH
Description:
Setting Policy:
This variable should only be set by the Group level and then
it should be unset in the environment part by the Site level.
Scope:
This variable should NOT be present in the user environment.
Example:
GROUPMANPATH="/afs/cern.ch/group/c3/man"
GROUPPATH
Description:
The path where are stored the Group binary files.
Setting Policy:
This variable should only be set by the Group level and then
it should be unset in the environment part by the Site level.
Scope:
This variable should NOT be present in the user environment.
Example:
GROUPPATH="/afs/cern.ch/group/c3/bin"
HOST
Description:
hostname (without domain-name)
Setting Policy:
This variable should only be set by the HEP level.
Scope:
This variable should be present in the user environment.
Example:
HOST="dxcern"
INITIALE
Description:
This is set to the first letter of the user name.
The first letter of the user name.
Setting Policy:
This variable should only be set by the Site level and should be unset
afterwards.
Scope:
This variable should NOT be present in the user environment.
Example:
INITALE=`echo $USER | cut -c1`
INITIALISED
Description:
This is used by CORE environment.
Setting Policy:
This variable should be set by the Site level.
Scope:
This variable should be present in the user environment.
Example:
INITIALISED="YES"
LD_LIBRARY_PATH
Description:
The path to reach the shared libraries (On Sun systems only).
Setting Policy:
This variable can be set at any level. Usually it should only be set
by HEP, Site, System and Cluster levels.
Scope:
This variable should be present in the user environment.
Example:
LD_LIBRARY_PATH="/opt/SUNWspro/lib:/usr/openwin/lib:/usr/dt/lib:/usr/local/lib"
LESSCHARSET
Description:
The character set for less.
You may define your own less commands by using the program
lesskey to create a file called ".less" . This file
specifies a set of command keys and an action associated
with each key.
The key bindings for less can be loaded with the -k option.
Example:
LESS="-e -i -M -w -k/usr/local/lib/less/.less"For the explanation of the other options consult the man page for less.
LESSCHARSET="latin1"
MAIL
Description:
incoming mailbox is set to the full path of your incoming
mailbox file.
Setting Policy:
This variable can be set at any level. Usually it is set by the HEP,
Site, System and Cluster levels.
Scope:
This variable should be present in the user environment.
Example:
MAIL="/afs/cern.ch/mail/$INITIALE/$USER/spoolfile"
MAILBOX
Description:
Setting Policy:
This variable can be set at any level. Usually it is set by the HEP,
Site, System and Cluster levels.
Scope:
This variable should be present in the user environment.
Example:
MAILBOX="$MAIL"
MAILSERVER
Description:
This variable specifies the name of the user IMAP or POP server.
Setting Policy:
This variable can be set at any level. Usually it is set by the HEP,
Site, System and Cluster levels.
Scope:
This variable should be present in the user environment.
Example:
MAILSERVER="mail.cern.ch"
MANPATH
Description:
lists where you can find manual pages used by commands like man
and xman.
Setting Policy:
This variable can be set at any level. Usually it is set by the HEP,
Site, System and Cluster levels.
Scope:
This variable should be present in the user environment.
Example:
MANPATH="$HOME/man:/usr/sue/man:/afs/usr/man:/usr/man:/usr/local/man:/cern/man"
NNTPSERVER
Description:
The NNTP server address.
One variable which should be set is the NNTPSERVER
which indicates which server should be contacted for
news reading, posting, etc. This variable is used by all
known newsreaders.
Setting Policy:
This variable can be set at any level. Usually it is set by the HEP,
Site, System and Cluster levels.
Scope:
This variable should be present in the user environment.
Example:
NNTPSERVER="news.cern.ch"
ORACLE*
Description: The oracle environment is available. It can be set from the user recommended templates by uncommenting a few lines.
It provides a list of variables which are mandatory to work
with oracle and to access the database. As it is not available
on all the platforms, you won't get it everywhere. Consult
the Oracle support group for more information.
Setting Policy:
This variable can be set at any level.
OS
name of the operating system (close to uname)
is the name of the operating system obtained usually with uname.
- HAS TO BE SET -
Setting Policy:
This variable should only be set at HEP and Site level.
Scope:
This variable MUST be present in the user environment.
Example:
OS="AIX"
PAGER
Description:
The default pager to read the man pages.
Setting Policy:
This variable can be set at any level.
Scope:
This variable should be present in the user environment.
Example:
PAGER="less"
PATH
Description:
Setting Policy:
This variable can be set at any level using the USERPATH variable.
Once USERPATH is evaluated, at the end, the HEP level builds the
PATH variable and the Site level removes any \\\$GROUPPATH not
expanded.
Scope:
This variable MUST be present in the user environment.
Example:
PATH="$HOME/bin $HOME/scripts "\\\$GROUPPATH" /usr/sue/bin $SYSPATH /usr/local/bin $X11BIN /cern/pro/bin ."
RFASSIGN
Description:
The rfassign variable (for RFIO).
Setting Policy:
This variable can be set at any level. It is usually done by the
Site level.
Scope:
This variable should be present in the user environment.
Example:
RFASSIGN="$HOME/.rfassign"
ROOTPATH
Description:
This path is the search path for the root user.
- HAS TO BE SET -
Setting Policy:
This variable must be set by the HEP and or Site level.
Scope:
This variable should NOT be present in the user environment.
Example:
ROOTPATH="/usr/bin /etc /usr/sbin /usr/ucb /usr/bin/X11 /sbin"
RUBOUT
(see rubout)
Description:
defines the RUBOUT sequence which is defined for your keyboard.
It can be set to BackSpace or Delete and can be modified by the
user with a file $HOME/.BackSpace or $HOME/.Delete.
On DEC VT terminals, the del (delete) key has always
been used as a rubout key, i.e., to delete the previous character.
The backspace key on VT terminals is designed to move the cursor
back one space on the line WITHOUT deleting the previous character.
(A DEC VT terminal does NOT have a key specifically designed to
delete the character directly under the cursor).
On IBM PC keyboards backspace is used as rubout key, not
the delete key. This left the word "delete" to be used for the
"delete the character under the cursor" function on the keypad.
Setting Policy:
This variable can be set at any level. It is usually done by the
Site level.
Scope:
This variable should be present in the user environment.
Example:
RUBOUT="BackSpace"
SYSMAN
Description:
Setting Policy:
This variable is set at HEP or Site level.
Example:
SYSMAN="/opt/SUNWspro/man:/usr/man:/usr/openwin/man:/usr/dt/man"
SYSPATH
Description:
System Path
Setting Policy:
This variable is set at HEP or Site level.
Scope:
This variable should NOT be present in the user environment.
Example:
SYSPATH="/usr/bin /usr/bin/X11 /usr/ucb"
SYSTYPE
Description:
reflects the flavor of the UNIX system:
sysV for system V,
bsd for BSD UNIX systems
Setting Policy:
This variable is set at HEP or Site level.
Scope:
This variable MUST be present in the user environment.
Example:
SYSTYPE="sysV"
USER
Description:
username
Setting Policy:
This variable should be present and is set at HEP level, only
if it wasn't defined before the HEPiX started.
Scope:
This variable MUST be present in the user environment.
Example:
USER="taddei"
USERPATH
Description:
This path is the search path for a normal user.
- HAS TO BE SET -
Setting Policy:
This variable can be set by any level. Usually Group level
is using GROUPPATH to insert correctly their Group PATH in the
well defined Site level USERPATH.
Scope:
This variable should NOT be present in the user environment but
its value is found in the PATH variable.
Example:
USERPATH="$HOME/bin $HOME/scripts "\\\$GROUPPATH" /usr/sue/bin $SYSPATH /usr/local/bin $X11BIN /cern/pro/bin ."
VISUAL
Description:
The default visual.
Setting Policy:
This variable can be set by any level.
Scope:
This variable should be present in the user environment.
Example:
VISUAL="pico -w"
WWW_HOME
Description:
The WWW home page address.
One example of a variable which can be set for Mosaic,
Netscape, etc. is the WWW_HOME variable.
This variable could be made group dependent for example.
Setting Policy:
This variable should can be set by any level.
Scope:
This variable should be present in the user environment.
Example:
WWW_HOME="http://www.cern.ch"
X11BIN
Description:
This resource sets where should be accessed the X11 applications.
Setting Policy:
This variable can be set by any level.
Scope:
This variable should NOT be present in the user environment.
Example:
X11BIN="/usr/local/bin/X11"
XFILESEARCHPATH
Description:
The variable for the X environment.
Setting Policy:
This variable can be set by any level. Usually it is done by the
Site level.
Scope:
This variable should be present in the user environment.
Example:
XFILESEARCHPATH="/usr/lib/X11/app-defaults/%N:/usr/local/lib/X11/app-defaults/%N"
YP
Description:
Status of NIS. This value of this variable reflects the status
of NIS (Yellow Pages). The known valuesare YES or NO
It is set automatically at the HEP level according to the value of
DOMAINNAME.
Setting Policy:
This variable should only be set by the HEP or the Site level.
Once used it should be removed.
Scope:
This variable should be present in the user environment.
Example:
YP="NO"
Arnaud Taddei, 8-Jul-1996