Using an alternative temporary directory with Intel Cluster Checker

Intel® Cluster Checker uses the standard temporary directory (/tmp) during installation and at runtime.  In some cases, /tmp may not be sufficient size, for example on a diskless cluster, or system policy may prefer a different directory for temporary files.  This article describes how to specify an alternative directory in place of /tmp.


During installation, a temporary directory is needed to unpack and temporally store some files.  To use a different directory, follow these steps, replacing /other/tmp with the path to your alternative temporary directory.  The Release Notes contain information on how much temporary space is needed for installation.

Extract the contents of the Intel Cluster Checker package: 

tar -xzf l_clck_p_<version>.<package#>.tar.gz -C /other/tmp

Run the installation script with the --tmp-dir command line option to specify the temporary directory:

cd /other/tmp/l_clck_p_<version>.<package#>
./install/sh --tmp-dir /other/tmp

After Intel® Cluster Checker has been successfully installed, you may wish to delete the temporary files extracted in the first step.  WARNING: you must always be cautious when deleting files.  The following command will delete all files and sub-directories in the specified directory.  If you have other files at this location, you should not run this command.

rm -rf /other/tmp/l_clck_p_<version>.<package#>

Runtime: Head Node

Intel® Cluster Checker creates many temporary files during its execution, on both the head node and the compute nodes. 

On the head node, the tool normally decompresses its runtime libraries to /tmp.  This location can be changed by setting the TEMP environment variable.  An absolute path should always be used and the directory should have read, write, and execute permissions for the user running Intel® Cluster Checker. The following example shows how to set this environment variable for the bash shell:

export TEMP=/export/home/icr

Runtime: Compute Nodes

Some test modules need to copy files to and from the compute nodes (e.g., benchmark binaries, source code, output files).  Again, by default, /tmp is used for these files.  This location can be defined with either a configuration option or an environment variable.  The following examples show the two ways to specify the temporary directory.

The XML configuration option <node_tempdir> may be used to specify an alternative temporary directory.  

Alternatively, the CLCK_NODE_TEMPDIR environment variable may be used.  For example:

export CLCK_NODE_TEMPDIR=/export/home/icr

If both the XML configuration option and the environment variable are set, the environment variable will used.
For more complete information about compiler optimizations, see our Optimization Notice.