Setting TMPDIR: Difference between revisions
(Created page with " <source lang='bash'> mkdir /lustre/scratch/WUR/ABGC/[user]/tmp </source> <source lang='bash'> export TMPDIR=/lustre/scratch/WUR/ABGC/[user]/tmp </source>") |
No edit summary |
||
Line 1: | Line 1: | ||
Many programs require writing intermediary or temporary information. A process may even require writing to a temporary location without a user knowing it. For instance, the command <code>sort</code>, part of the <code>bash</code> toolkit, requires a lot of temporary file space when sorting large volumes of data. Often programs take the system default, which is usually <code>/tmp</code> on Linux systems. The <code>/tmp</code> partition is however often too limited in size and can get filled up. When this happens all users that require write access to <code>/tmp</code> will experience problems in running jobs, which can range from unexpected quitting of processes, to erroneous output. | |||
<source lang='bash'> | <source lang='bash'> |
Revision as of 14:43, 8 December 2013
Many programs require writing intermediary or temporary information. A process may even require writing to a temporary location without a user knowing it. For instance, the command sort
, part of the bash
toolkit, requires a lot of temporary file space when sorting large volumes of data. Often programs take the system default, which is usually /tmp
on Linux systems. The /tmp
partition is however often too limited in size and can get filled up. When this happens all users that require write access to /tmp
will experience problems in running jobs, which can range from unexpected quitting of processes, to erroneous output.
<source lang='bash'>
mkdir /lustre/scratch/WUR/ABGC/[user]/tmp
</source>
<source lang='bash'> export TMPDIR=/lustre/scratch/WUR/ABGC/[user]/tmp </source>