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:<jobid>) would be a good idea.
b) The orte-ps command output to use the same jobid format.
c) A more easily parsable output format from ompi-ps. It doesn't need to be a full blown XML format, just something like the following would suffice:
I'd be happy to help with any or all of these.
On Jul 22, 2011, at 10:18 AM, Ralph Castain wrote:
> 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 <jobid>:<uri>. As the -h option indicates:
> -report-uri | --report-uri <arg0>
> Printout URI on stdout [-], stderr [+], or a file
> [anything else]
> The "jobid" required by the orte-ps command is the one reported there. We could easily add a --report-jobid option if that makes things easier.
> As to the difference in how orte-ps shows the jobid...well, that's probably historical. orte-ps uses an orte utility function to print the jobid, and that utility always shows the jobid in component form. Again, could add or just use the integer version.
> On Jul 22, 2011, at 7:01 AM, Greg Watson wrote:
>> 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?
>> devel mailing list
> devel mailing list