I have a long running Torque/PBS job and I'd like to monitor output. But log file only gets copied after the job is finished. Is there a way to convince PBS to refresh it?
相关问题
- multidplyr : assign functions to cluster
- Spring Batch - late binding of commit interval not
- Parallel for loop over range of array indices in C
- Parallel downloads with Multiprocessing and PySftp
- Using more worker processes than there are cores
相关文章
- How to use doMC under Windows or alternative paral
- Parallel while loop in R
- Does gfortran take advantage of DO CONCURRENT?
- Using Parallel Linq Extensions to union two sequen
- MPI and D: Linker Options
- Is there an existing solution for these particular
- SqlConnection closes unexpectedly inside using sta
- On a 64 bit machine, can I safely operate on indiv
This is possible in TORQUE. If you have a shared filesystem you can set
$spool_as_final_name true
in the mom's config file. This will have the file write directly to the final output destination instead of spooling in the spool directory. Once you are set up with that you can tail -f the output file and monitor anything you want.
http://www.adaptivecomputing.com/resources/docs/torque/3-0-3/a.cmomconfig.php (search for spool_as_final_name
In case you submit a shell script you may also put these two commands in the beginning of the script.
This will put the output from stdout and stderr in the working directory of your job.
For me, ssh-ing to the node where the job is running and looking at files under
/var/spool/torque/spool/
works, but it might be specific to this particular environment.Unfortunately, AFAIK, that is not possible with PBS/Torque - the stdout/stderr streams are locally spooled on the execution host and then transferred to the submit host after the job has finished. You can redirect the standard output of the program to a file if you'd like to monitor it during the execution (it makes sense only if the execution and the sumit hosts share a common filesystem).
I suspect the rationale is that it allows for jobs to be executed on nodes that doesn't share their filesystem with the submit node.