On Jul 22, 2011, at 3:57 PM, Greg Watson wrote:
> Hi Ralph,
>
> I'd like three things :-)
>
> a) A --report-jobid option that prints the jobid on the first line in a form
> that can be passed to the -jobid option on ompi-ps. Probably tagging it in
> the output if -tag-output is enabled (e.g.
The output below resulted from an attempt to start a job w/checkpoint
support when the BLCR kernel modules were not loaded on then node
("pilot error"). The mistake is mine, but I am reporting this because
there appears to be more going on in the output than probable should be
- the following
Hi Ralph,
I'd like three things :-)
a) A --report-jobid option that prints the jobid on the first line in a form
that can be passed to the -jobid option on ompi-ps. Probably tagging it in the
output if -tag-output is enabled (e.g. jobid:) would be a good idea.
b) The orte-ps command output to
I was supposed to send this earlier this week, but in the hustle and bustle of
the MPI Forum, I didn't get to it until now. Sorry, folks!
It seems that we're missing another major ARM assembly file (my ARM contact
just pinged me earlier saying that he finally tested again today and found that
Hmmm...well, it looks like we could have made this nicer than we did :-/
If you add --report-uri to the mpirun command line, you'll get back the uri for
that mpirun. This has the form of :. As the -h option indicates:
-report-uri | --report-uri
Printout URI on stdou
Hi all,
Does anyone know if it's possible to get the orte jobid from the mpirun
command? If not, how are you supposed to get it to use with orte-ps? Also,
orte-ps reports the jobid in [x,y] notation, but the jobid argument seems to be
an integer. How does that work?
Thanks,
Greg
