Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

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.

Subject: Re: [hwloc-devel] Priority of env vars vs. application options
From: Samuel Thibault (samuel.thibault_at_[hidden])
Date: 2009-10-28 09:21:27

Jeff Squyres, le Wed 28 Oct 2009 09:16:26 -0400, a écrit :
> I would think that consistency across all tools is best:
> - command line
> - env variable
> - compiled-in defaults
> If you're in an environment where you can't pass command line options,
> then use the environment (either explicitly set or unset it).

But what about the situation that Brice suggested, i.e. the application
itself using xml files internally? Where in the list should that be?