Leftover files in /tmp

Get Help
1

I noticed that the simple VNC application which I installed on my cluster closely following the official documentation, leaves many files in /tmp/dbus-* and sometimes even in /tmp/X1*-lock

The former don’t seem to create any problem (they are even zero-sized, even though one could run out of inodes), but the latter prevent further jobs on the same node from starting correctly. The problem is occasional (I have not been able to track it down), and I have seen the related discussion at Lock files for VNC-based apps not being cleaned up

Is there a best practice to prevent these files from accumulating? I know I can use the slurm epilogue and/or the OOD cleaner, but I’m looking for advice of what is the best approach for this and perhaps for a nudge to include such advice in the documentation (or make it more prominent, if it’s already there and I overlooked it).

Thanks

2

If you use SLURM, you can try Slurm Workload Manager - job_container.conf . That is basically polyinstantiation on the compute nodes for temp directories and would likely solve this problem for any job, not just OOD.

1 Like
3

Thank you @maflister! Yes that’s the same advice I would have given. It’ll give every job their own tmpfs tmp directory that disappears after the job completes.

4

Thanks so much folks!