FAQ
From FarmShare
(Difference between revisions)
(New page: #'''tset: standard error: Invalid argument''' In your job script, you probably don't explicitly specify which shell to use. Probably your default shell is csh and your csh startup scripts...) |
|||
| Line 1: | Line 1: | ||
| - | + | *'''tset: standard error: Invalid argument''' | |
In your job script, you probably don't explicitly specify which shell to use. Probably your default shell is csh and your csh startup scripts are getting loaded and something there is generating that error because the job is not run under an interactive session. So the solution is to either specify a shell on the first line of your job script in the usual Unix way e.g. | In your job script, you probably don't explicitly specify which shell to use. Probably your default shell is csh and your csh startup scripts are getting loaded and something there is generating that error because the job is not run under an interactive session. So the solution is to either specify a shell on the first line of your job script in the usual Unix way e.g. | ||
| + | |||
#!/bin/bash | #!/bin/bash | ||
| + | |||
or else use the -S flag to qsub, e.g. | or else use the -S flag to qsub, e.g. | ||
| - | #'''tty errors''' | + | # get rid of spurious messages about tty/terminal types |
| + | #$ -S /bin/sh | ||
| + | |||
| + | *'''tty errors''' | ||
You may see things like | You may see things like | ||
<pre> | <pre> | ||
| Line 18: | Line 23: | ||
</pre> | </pre> | ||
| - | See the question above, and specify a shell. | + | See the question above, and specify a shell. See the 'shell_start_mode' section of 'man sge_conf' for more info. |
Revision as of 19:07, 2 November 2011
- tset: standard error: Invalid argument
In your job script, you probably don't explicitly specify which shell to use. Probably your default shell is csh and your csh startup scripts are getting loaded and something there is generating that error because the job is not run under an interactive session. So the solution is to either specify a shell on the first line of your job script in the usual Unix way e.g.
#!/bin/bash
or else use the -S flag to qsub, e.g.
# get rid of spurious messages about tty/terminal types #$ -S /bin/sh
- tty errors
You may see things like
tset: standard error: Invalid argument Undefined tty stdin: is not a tty
or
Warning: no access to tty (Bad file descriptor). Thus no job control in this shell.
See the question above, and specify a shell. See the 'shell_start_mode' section of 'man sge_conf' for more info.
