| Line 10: |
Line 10: |
| | | | |
| | This will display | | This will display |
| − | *the process ID | + | *ID: the process ID |
| − | *the owner of the job | + | *OWNER: the owner of the job |
| − | *the date and time it was submitted | + | *SUBMITTED: the date and time it was submitted |
| − | *how long it has been running | + | *RUN_TIME: how long it has been running |
| − | *its current status (run, held, idle) | + | *ST: its current status (run R, held H , idle I) |
| − | *the job size | + | *SIZE: the job size |
| − | *program name | + | *CMD: program name |
| | | | |
| | This is useful to monitor your own jobs to check on their status. | | This is useful to monitor your own jobs to check on their status. |
| Line 30: |
Line 30: |
| | Another useful command is <i>condor_status</i> which can tell you information about the cluster machines | | Another useful command is <i>condor_status</i> which can tell you information about the cluster machines |
| | <pre> | | <pre> |
| − | [username@computer ~]$ condor_status [-r] | less | + | [username@computer ~]$ condor_status [-r] | grep stat | less |
| | </pre> | | </pre> |
| | | | |
| Line 36: |
Line 36: |
| | | | |
| | If there are any concerns about a specific job, please contact the main administrator. | | If there are any concerns about a specific job, please contact the main administrator. |
| | + | |
| | + | == Check the job as it runs == |
| | + | === Check stdout === |
| | + | If a job is running you can execute the following command to see the tail of the stdout file |
| | + | |
| | + | <pre> |
| | + | condor_tail <job_id> |
| | + | </pre> |
| | + | |
| | + | === Check stderr === |
| | + | If you want to see if there are any errors you can run the following |
| | + | |
| | + | <pre> |
| | + | condor_tail -no-stdout -stderr <job_id> |
| | + | </pre> |