Why /tmp?

From Cornell CAC Documentation

Revision as of 18:54, 6 January 2012 by Jhs43 (Talk | contribs)
Jump to: navigation, search

Using a temporary directory

It is faster to perform local file I/O and copy complete data files to/from $HOME at the beginning and the end of the job, rather than perform I/O over the network ($HOME is network mounted on the compute nodes).

  • /tmp cleanup policy: At this time atlas does not have a /tmp cleanup policy outside the /tmp/$PBS_JOBID deletion at job end.
  • Torque creates a uniquely named directory (/tmp/$PBS_JOBID) when a job starts and stores the path of this directory in the $TMPDIR environment variable. This directory is cleaned up when the job exits.
    • To use this feature, reference $TMPDIR
  • You may create directories for file read/writes outside your /tmp/$PBS_JOBID in /tmp. You do risk leaving any data there; it may be deleted at any time we see /tmp getting full.
Retrieved from "http://www.cac.cornell.edu/wiki/index.php?title=Why_/tmp%3F"
Personal tools