- Download the TORQUE distribution file from http://clusterresources.com/downloads/torque (CHANGELOG)
- Extract and build the distribution on the machine that will act as the "TORQUE server"
- the machine that will monitor and control all compute nodes by running the pbs_server daemon. See the example below (where XXX stands for the latest distribution (e.g., "-1.2.0p4"):
> tar -xzvf torqueXXX.tar.gz
> cd torqueXXX
> make install
- (OPTIONAL) Set the PATH environment variable. The default installation directories for the binaries are either /usr/local/bin and /usr/local/sbin
||In this document $(TORQUECFG) corresponds to where TORQUE stores its configuration files. This defaults to /usr/spool/PBS.
||TORQUE 2.0p2 and higher includes a standard spec file for building your own rpms. It is also possible to use the checkinstall program to create your own RPM, tgz, or deb package.
TORQUE has two main executable files, one for the head node pbs_server and one for each of the compute nodes pbs_mom.
Therefore, TORQUE needs to be installed on a head node, every machine that jobs will run on and any machines that commands will be called from.
When a job is run, the first node that the job is run on is designated as the Mother Superior.
All other nodes for that job are designated as sister moms.
1.1.1 Compute Nodes
To install TORQUE on a compute node do the following on each machine (see page 19, Section 3.2.1 of PBS Administrator's Manual for full details):
- Create the self-extracting, distributable packages with make packages (See the INSTALL file for additional options and features of the distributable packages) and use the parallel shell command from your cluster management suite to copy and execute the package on all nodes (ie: xCAT users might do prcp torque-package-linux-i686.sh main:/tmp/; psh main /tmp/torque-package-linux-i686.sh --install. Optionally, distribute and install the clients package.
- Although optional, it is also possible to use the TORQUE server as a compute node and
install a pbs_mom alongside the pbs_server daemon.
Example: Compute Node Installation
> make packages
Building ./torque-package-clients-linux-i686.sh ...
Building ./torque-package-mom-linux-i686.sh ...
Building ./torque-package-server-linux-i686.sh ...
Building ./torque-package-gui-linux-i686.sh ...
Building ./torque-package-devel-linux-i686.sh ...
The package files are self-extracting packages that can be copied
and executed on your production machines. Use --help for options.
> cp torque-package-mom-linux-i686.sh /shared/storage
> cp torque-package-clients-linux-i686.sh /shared/storage
> dsh /shared/storage/torque-package-mom-linux-i686.sh --install
> dsh /shared/storage/torque-package-clients-linux-i686.sh --install
||Both pbs_iff and pbs_rcp will be installed suid root.
1.1.2 Enabling TORQUE/Moab as a Service (OPTIONAL)
Optional startup/shutdown service scripts are provided as an example of how to run TORQUE as an OS service that starts at bootup. The scripts are located in the contrib/init.d/ directory of the TORQUE tarball you downloaded. In order to use the script you must:
- Determine which init.d script suits your platform the best.
- Modify the script to point to TORQUE's install location. This should only be necessary if you used a non-default install location for TORQUE (by using the --prefix option of ./configure).
- Place the script in the /etc/init.d/ directory.
- Use a tool like chkconfig to activate the start-up scripts or make symbolic links (S99moab and K15moab, for example) in desired runtimes (/etc/rc.d/rc3.d/ on Redhat, etc.).