next up previous contents
Next: Installation in enforced Up: The HEPiX Shells and Previous: Introduction

Installation

The HEPiX login scripts can be installed into 2 modes:

Indeed we considered two target situations:

The initial target of this package was the new systems as we wanted to provide a good and standardised environment to users for all the new services; but as a side effect, the deployment of this package affects the 'old' services as well. Although it is possible to enforce an environment each time a user starts a shell on a new service, it is probably not wise to do on an existing service where a certain number of users are not used to this new environment. Thus, in the latter case, the environment should not be enforced and the user should have the choice whether to start the HEPiX login scripts or not.

How is it possible to enforce an environment? Simply by configuring a certain number of shell configuration files under /etc on a system. This does not work for all shells gif and this is why we provide a default template file for each shell which has to be used by the user. In these templates a central auxiliary file is called and checks if the HEPiX scripts have already been started and if not it runs them gif .

Thus depending on your case, the installation procedure will put some files under /etc (in enforced mode) or not (in weak or non-enforced mode).

Once you have stated that you are in situation where you are dealing with a new or an existing service, you can install the package by following the installation in enforced or weak mode.

Warning: perl 4 is required and it is expected that the binary is under
        /usr/local/bin/perl
with its libraries under
        /usr/local/lib/perl
It is required both for the installation and the usage of the HEPiX shells and X11 login scripts.

The default and the recommendation for installing this HEPiX package is to install the shells login scripts locally on the machines file systems and in enforced mode. This means that you should install the etc, hepix, bin and man1 collections (see table 1).

For system administrators who want to trace the behaviour of the HEPiX scripts, they can use the so-called debug mode installation. It means that each time a user will start a shell, a log file will be produced under /tmp. The naming scheme of these files is:

       /tmp/hepix-log.$USER.$$
The same apply for the HEPiX X11 login scripts in debug mode a file
       /tmp/hepix-X-log.$USER.$$
is produced each time the user is doing an Xsession or is starting an Xsession in fake mode.
So, be very carefull while using this mode and make sure that /tmp is cleaned periodically! You must understand that this mode is only used to debug problems. Never use it in production services!




next up previous contents
Next: Installation in enforced Up: The HEPiX Shells and Previous: Introduction



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