use /var/tmp instead on /tmp for storing job runtime information

[GoogleCodeExporter]

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

Please use labels and text to provide additional information.

Original issue reported on code.google.com by sergio.m...@gmail.com on 21 May 2014 at 7:27

[GoogleCodeExporter]

...hit "enter" before editing...

anyhow, 
we need to move the job's session folder from /tmp to /var/tmp as in the former 
case, when a job is hosted on a VM and for whatever reason the VM reboots, the 
/tmp folders gets wiped out so, even if the job is completed, it is not 
possible to retrieve its results.

S.

Original comment by sergio.m...@gmail.com on 21 May 2014 at 7:29

• Changed title: use /var/tmp instead on /tmp for storing job's session
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

(Nitpick: it's not the "session folder" that is stored in `/tmp`)

Original comment by riccardo.murri@gmail.com on 21 May 2014 at 8:36

• Changed title: use /var/tmp instead on /tmp for storing job runtime information

[GoogleCodeExporter]

in release 3926

Original comment by sergio.m...@gmail.com on 21 May 2014 at 10:59

• Changed state: Fixed