On Jun 13, 2005, at 8:23 AM, Pierre Valiron wrote:
>>> Of course there is a workaround using
>>>
>>> export LAM_MPI_SESSION_PREFIX="/some/permanent/path"
>>> export LAM_MPI_SESSION_SUFFIX="some_unique_name"
>>
>> I'm a little confused -- this should suffer exactly the same problem
>> as you described above. The mechanism for where LAM's session
>> directory is located/found does not affect the takedown time of
>> lamhalt.
>
> I don't agree.
>
> If the daemons are attached to a volatile directory, lamhalt comes into
> trouble when the directory is destroyed. If the deamons are attached to
> a permanent one, then lamhalt gets all the time he needs to kill the
> lam
> universe and remove the corresponding files.
Unfortunately, I'm still confused. :-)
Are you saying that you're removing $TMPDIR before running lamhalt? Or
perhaps removing it immediately after lamhalt completes? If so, then
yes, I would agree -- lamhalt will have problems because the socket
that it's looking for will no longer exist. In either case, a "sleep
3" after the lamhalt command should fix the problem.
Did you mean something else?
--
{+} Jeff Squyres
{+} jsquyres_at_[hidden]
{+} http://www.lam-mpi.org/
|
