Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Andes job script stdout/stderr file specifications #327

Open
secondspass opened this issue Nov 23, 2020 · 0 comments
Open

Andes job script stdout/stderr file specifications #327

secondspass opened this issue Nov 23, 2020 · 0 comments

Comments

@secondspass
Copy link
Contributor

In the Common Batch Options to Slurm section in Andes, we talk about the -o and -e flags. That section seems to imply that if we don't use -o or -e, the output is automatically saved to a file with the filename <job_script>.o$SLURM_JOB_UID. This is actually not the case. By default both standard output and standard error are directed to a file of the name "slurm-%j.out", where the "%j" is replaced with the job allocation number.

Also, we should provide some guidance on using some commonly used filename patterns like %j for the -o and -e files (current documentation doesn't provide that information).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant