Taking a quick look at the commits it seems that r18037 looks like
the most likely cause of this problem.
Previously the session directory was forced to "/tmp" if no
environment variables were set. This revision removes this logic and
uses the opal_tmp_directory(). Though I agree with this change, I
think the logic for selecting the TMP directory should be extended to
use '/tmp' if it exists. If it does not then the home directory
should be a fine last alternative.
How does that sound as a solution? This would prevent us from
unexpectedly changing our running behavior in user environments in
which none of those variables are set.
On Mar 31, 2008, at 4:01 PM, Josh Hursey wrote:
> Nope. None of those environment variables are defined. Should they
> be? It would seem that the last part of the logic should be (re-)
> extended to use /tmp if it exists.
> -- Josh
> On Mar 31, 2008, at 3:51 PM, George Bosilca wrote:
>> I looked over the code and I don't see any problems with the
>> changes. The only think I did is replacing the getenv("HOME") by
>> opal_home_directory ...
>> Here is the logic for selecting the TMP directory:
>> if( NULL == (str = getenv("TMPDIR")) )
>> if( NULL == (str = getenv("TEMP")) )
>> if( NULL == (str = getenv("TMP")) )
>> if( NULL == (str = opal_home_directory()) )
>> str = ".";
>> Do you have any of those (TMPDIR, TEMP or TMP) in your environment ?
>> On Mar 31, 2008, at 3:13 PM, Josh Hursey wrote:
>>> So does anyone know why the session directories are in $HOME instead
>>> of /tmp?
>>> I'm using r18044 and every time I run the session directories are
>>> created in $HOME. George does this have anything to do with your
>>> commits from earlier?
>>> -- Josh
>>> devel mailing list
>> devel mailing list
> devel mailing list