The
environment propagation change to Cheyenne made on October 27 has important implications for some users’ jobs. Before that change was made to facilitate the new peer-scheduling capability, your Cheyenne environment settings – including set variables and loaded modules – were propagated by default from your login shell at submission time. That is no longer the case. Please keep this in mind if you see odd behaviors or job failures.
The new PBS job initialization process starts an interactive login shell for interactive jobs and a non-interactive shell for batch jobs. To be consistent with Casper, Cheyenne jobs now source your login initialization scripts:
~/.tcshrc for
tcsh/csh users and
~/.profile for
bash users. Review our
Personalizing start files documentation for examples and recommended practices.
You can propagate your Cheyenne environment settings if necessary by specifying -V to qsub at submission time, but that is incompatible with peer scheduling; jobs submitted from Casper to Cheyenne using -V will fail. Recommendations:
- If you need to set specific variables outside of the job environment, forward those variables using the lowercase -v VAR1,VAR2 argument to qsub.
- If you previously sourced an environment preparation script before submitting your batch job – to load modules, for example – source the script within the batch job instead.