Htc test local: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
You must first login to a user interface (testumd-ui01.wn). Don't forget to switch to an ordinary user if you reached the user interface as root! | You must first login to a user interface (testumd-ui01.wn). Don't forget to switch to an ordinary user if you reached the user interface as root! | ||
Create a sub file. Here is an example: | Create a sub file. Here is an example (sleep.sub): | ||
<pre> | <pre> | ||
executable = sleep.sh | executable = sleep.sh | ||
Line 13: | Line 13: | ||
queue | queue | ||
</pre> | </pre> | ||
You must then create the mentioned sleep.sh: | |||
<pre> | |||
#!/bin/bash | |||
# file name: sleep.sh | |||
id | |||
pwd | |||
TIMETOWAIT="6" | |||
echo "sleeping for $TIMETOWAIT seconds" | |||
/bin/sleep $TIMETOWAIT | |||
/usr/bin/hostname -f | |||
</pre> | |||
You can now submit the job: | |||
<pre> | |||
condor_submit sleep.sub | |||
</pre> | |||
Check the status of the job with the command: | |||
<pre> | |||
condor_q | |||
</pre> | |||
In case of troubles, you can have a look at the log file mentioned in the *.sub (sleep.log in this example). | |||
When the job is finished, you should find the output (outfile.txt) and error (errors.txt) files in the current directory. |
Revision as of 12:27, 31 July 2020
A simple local submission test
You must first login to a user interface (testumd-ui01.wn). Don't forget to switch to an ordinary user if you reached the user interface as root!
Create a sub file. Here is an example (sleep.sub):
executable = sleep.sh log = sleep.log output = outfile.txt error = errors.txt should_transfer_files = Yes when_to_transfer_output = ON_EXIT RequestMemory = 947 queue
You must then create the mentioned sleep.sh:
#!/bin/bash # file name: sleep.sh id pwd TIMETOWAIT="6" echo "sleeping for $TIMETOWAIT seconds" /bin/sleep $TIMETOWAIT /usr/bin/hostname -f
You can now submit the job:
condor_submit sleep.sub
Check the status of the job with the command:
condor_q
In case of troubles, you can have a look at the log file mentioned in the *.sub (sleep.log in this example).
When the job is finished, you should find the output (outfile.txt) and error (errors.txt) files in the current directory.