PBS currently writes the stdout and stderr files to PBS_HOME/spool or to the users home directory (if –koe option is used). This ticket is to add a new option such that the output (stdout/stderr) files go to the final destination, instead of being staged, if the final destination is known to be writable from the job execution node.
1 A user would like to have the option to have their job’s output (.o and .e) files to be written to the final destination, if the file system is available from mother superior, instead of being staged.
2 A user would like to see their job output in submission directory or directory specified via existing -o and/or -e qsub options as it is running to verify that it is running properly.
3 Admins would like the option for the .o and .e files from users jobs to go to their final destination automatically when possible, instead of staging them from PBS_HOME/spool directory, to avoid filling up PBS_HOME on the nodes.
4 The admin would like the option, at the site level, to prohibit this new behavior and instead stage the job output files instead of writing them to the final destination as the job is running.
5 A user would like the ability to tell PBS to remove the .o and .e files if the job exited without an error.
1 CRIT PBS shall optionally write a job's output and error files to their final destination, bypassing PBS_HOME/spool, if the final destination is known to be writable from mother superior.
2 CRIT The user shall be able to enable this functionality on a per job basis.
3 CRIT The admin shall be able to enable this functionality by default.
4 CRIT The current default behavior of staging the output instead of writing the output to the final destination as the job is running is retained, the new behavior is opt-in.
5 HIGH A user shall be able to provide an option at job submission time to have PBS remove the output files (.o and .e) for that job, if it completes successfully.
6 MED An admin shall be able to disable this new behavior.