Isn't this problematic if the user specifies a path that doesn't exist or gets deleted before the job schedules? It might be nice to have a spooling option or a fallback directory option if the target directory/file doesn't exist or can't be opened. Right now I think the output just goes into the bit bucket.
Bill. -- Bill Barth, Ph.D., Director, HPC [email protected] | Phone: (512) 232-7069 Office: ROC 1.435 | Fax: (512) 475-9445 On 9/10/14, 8:39 PM, "Christopher Samuel" <[email protected]> wrote: > >On 10/09/14 03:10, Erica Riello wrote: > >> I would like to know where SLURM keeps undelivered output as well as the >> problems that can cause an output file not to be deliver. > >I think you must be coming from a Torque or PBS background where output >is spooled into a temporary directory and then copied back at the end of >the job. > >Slurm doesn't do that, it defaults to writing the output (and errors) to >a file in the directory a job is running in, so there's no need to copy >it back at the end of the job. > >Hope that helps, >Chris >-- > Christopher Samuel Senior Systems Administrator > VLSCI - Victorian Life Sciences Computation Initiative > Email: [email protected] Phone: +61 (0)3 903 55545 > http://www.vlsci.org.au/ http://twitter.com/vlsci
