[ Skip to the content ]

Institute of Formal and Applied Linguistics Wiki


[ Back to the navigation ]

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
grid [2020/05/06 14:44]
ufal [Other]
grid [2020/05/06 14:45] (current)
ufal [Other]
Line 333: Line 333:
   * You can use environment variables ''​$JOB_ID'',​ ''​$JOB_NAME''​.   * You can use environment variables ''​$JOB_ID'',​ ''​$JOB_NAME''​.
   * One job can submit other jobs (but be careful with recursive:​-)). A job submitted to the CPU cluster may submit GPU jobs (to the ''​qpu.q''​ queue).   * One job can submit other jobs (but be careful with recursive:​-)). A job submitted to the CPU cluster may submit GPU jobs (to the ''​qpu.q''​ queue).
-  * It is important, that the files that are sourced during a login such as .bash_profile,​ .profile, .bashrc, .login etc. don't produce any output when a non-interactive login is done. If they do, changes ​are that your job will run, but that the batch system is unable to deliver to you the standard output and error files. In that case the status of your job will be '​E'​ after the job is finished. Here is an example how you can test in a .bash_profile or .bashrc if this is an interactive login:+  * It is important, that the files that are sourced during a login such as .bash_profile,​ .profile, .bashrc, .login etc. don't produce any output when a non-interactive login is done. If they do, chances ​are that your job will run, but that the batch system is unable to deliver to you the standard output and error files. In that case the status of your job will be '​E'​ after the job is finished. Here is an example how you can test in a .bash_profile or .bashrc if this is an interactive login:
 <​code>​ <​code>​
 unset INTERACTIVE unset INTERACTIVE

[ Back to the navigation ] [ Back to the content ]