next up previous contents
Next: Customising the scripts Up: The HEPiX Shells and Previous: Warning - require

Customisation

In order to customise the HEPiX scripts you must understand the file layout and the HEPiX way of classifying the system administrators.

Figure 1 shows the main idea of the HEPiX scripts file layout.

  
Figure 1: The mechanical levels of the HEPiX scripts

Table 2 gives the list of the auxiliary files which are used to make the HEPiX scripts accessible.

Note that for HEPiX X11 login scripts the xdm wrappers are put under a directory:

        /usr/sue/lib/xdm
The sue directory resides on a local file system directory. It refers to the CERN SUE project (see [9]) although the HEPiX scripts package can be installed with the CERN SUE system, it doesn't require it. So, it had been decided that the xdm wrappers would go into this directory no matter if SUE exists or runs for the machine on which you are performing the installation.

  
Table 2: Auxiliary files

Table 3 gives the names of the files for each shell flavour and for the HEPiX-X11 part, at each level. They can be used to provide a customised environment which suites your needs.

So if you want to provide a customisation for the C-shells on the machine you administer, you simply have to add lines in the files whose names are in the column System level and in the raw C-shell.

Thus you can customise your environment using the following files in /etc/hepix for the C-shells:

  
Table 3: HEPiX file layout

Moreover, the user can use templates files. In each newly created account all the templates files for the customisation of the shell should be provided. This applies as well for the X11 customisation files under $HOME/.hepix. Each user can edit these files using the examples described in the previous section to customise their environments.

In these templates the user will find 3 parts:

1
the header part which gives the address mail in case of serious problems, the version number, the generation date, the authors, etc.
2
the hook to the HEPiX scripts. This hook is not required if the HEPiX scripts are installed in enforced mode. The user should anyway NEVER remove these 3 lines for the C-shell users
        if ( -r /usr/local/lib/hepix/central_env.csh ) then
           source /usr/local/lib/hepix/central_env.csh
        endif
or the following lines for the Bourne-shells users:
        if [ -r /usr/local/lib/hepix/central_env.sh ]; then
           . /usr/local/lib/hepix/central_env.sh
        fi
These lines might be slightly different in future versions.
3
commented lines. All these lines can be uncommented. They give users examples of what they can do and this is their part. They can use it, remove it, update it as they wish.

These templates give other examples and, for tcsh or zsh shells, there are other related documents like [5], [2], [3], [4].

In the following, the filename extension notation .[c]sh means that there are two such files one to customise the C shells (.csh) and the other to customise the Bourne shells (.sh).




next up previous contents
Next: Customising the scripts Up: The HEPiX Shells and Previous: Warning - require



Arnaud Taddei
Tue Dec 12 08:15:58 MET 1995