... | ... | @@ -97,4 +97,29 @@ However, in the case that the command exits abnormally, a value of 0200 (octal) |
|
|
to the value of the command to make up the exit status.
|
|
|
|
|
|
For example: If a job dies through signal 9 (SIGKILL) then the exit status becomes 128 + 9 = 137.
|
|
|
````
|
|
|
**Why does my script not run or returns an error `/bin/bash^M: bad interpreter: No such file or directory`**
|
|
|
* your script has been edited with an editor under windows, your line breaks for windows are` ^M` characters.
|
|
|
You can view your script file and check if you have these characters with the command:
|
|
|
`cat -v <script_name>`
|
|
|
|
|
|
```
|
|
|
#!/bin/bash^M
|
|
|
#$ -S /bin/bash^M
|
|
|
#$ -q all.q^M
|
|
|
#$ -cwd^M
|
|
|
#$ -V^M
|
|
|
#$ -j Y^M
|
|
|
^M
|
|
|
^M
|
|
|
date^M
|
|
|
hostname^M
|
|
|
```
|
|
|
to remove the `^M` use the command `dos2unix <file_name>`
|
|
|
|
|
|
* If you submit a script with the `^M` with qsub your job will get in an error state `Eqw`
|
|
|
If this happens you can see with the command `qstat -j <job_ID>` and error at the line : error reason
|
|
|
|
|
|
````
|
|
|
execvp(/var/spool/sge/silvertipshark/job_scripts/<job_id>, "/var/spool/sge/silvertipshark/job_scripts/<job_id>") failed: No such file or directory
|
|
|
```` |
|
|
\ No newline at end of file |