This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
On Apr 24, 2014, at 1:38 AM, Mike Dubman <miked_at_[hidden]> wrote:
> ** prefix each well-known MCA param with "print_":
I like the overall idea of this RFC, but I'm not wild about this specific word "print" -- it seems weird. All the MCA parameters are *printed* -- the word "print" doesn't really distinguish anything here.
(I know I'm just harping on a word, but I think it's an important word here... :-) )
Got a better suggestion, perchance? (I don't, offhand...)
> ** Define two well-known mca parameters indicating external library runtime and compiletime versions, i.e.:
> The following command will show all exposed well-known mca params from all components:
> ompi_info --parsable -l 9 |grep ":print_"
How about changing this a bit (hoping my regexp syntax is correct at 6:30am before coffee...):
ompi_info --all --parsable | egrep ':(compile|run)time_version'
Then the "print_" prefix isn't needed.
For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/