Hi there, On 08/11/16 21:21, Alexandre Strube wrote:
> For example, on slurm 10.05.6, the example config file says: > > StateSaveLocation=/tmp > > Which is not the best place to write sensitive information, but it will > for sure be there and will be writable by the slurm user. Frankly using /tmp seems like a *really* bad idea to me. The reason is that (depending on system configuration) may be cleaned up either on a reboot (either scripts or by using non-persistent tmpfs) or periodically using tmpwatch or similar scripts. So if you've got jobs queued for any period of time that information will be lost. We build from source and use: StateSaveLocation = /var/spool/slurm/jobs but the decision is yours where exactly to put it. But /tmp is almost certainly the second worst place (after /dev/shm). All the best, Chris -- Christopher Samuel Senior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci
