[MPICH] Re: New version of MPICH2 (1.0.2)

[James S Perrin]

Hi,
	There is a very simple way to get around this which I use and that is to run
your binaries indirectly via shell scripts. You can then set LD_LIBRARY_PATH in
the script as well as any other environment variables you may wish.

Regards
James

> Date: Sun, 12 Jun 2005 11:15:59 +0200
> From: Trach-Minh Tran <trach-minh.tran at epfl.ch>
> To: Rusty Lusk <lusk at mcs.anl.gov>
> Cc: mpich-discuss at mcs.anl.gov
> Subject: Re: [MPICH] Re: New version of MPICH2 (1.0.2)
>
> On 06/12/2005 08:04 AM, Trach-Minh Tran wrote:
> > On 06/12/2005 02:20 AM, Rusty Lusk wrote:
> >
> >>> - The mpdrun/mpirun did not export the current LD_LIBRARY_PATH
> >>> environment variable.
> >>>   It seems however that it does export the other variables (PATH,
> >>> PWD, ...) !
> >>>   Spawning the processes with mpdboot and mpirun from the 1.0.1
> >>> version appears to
> >>>   work with codes compiled with the 1.0.2 version!
> >>>
> >>
> >>
> >> You will want to use the MPI-2 standard 'mpiexec' instead of mpirun.
> >> By default, it should export all environment variables.  Let us know if
> >> it doesn't.
> >>
> > Both mpiexec and mpdrun fail to export LD_LIBRARY_PATH, as mpirun. It is
> > strange that it seems that all environment variables are exported *except*
> > LD_LIBRARY_PATH!
> >
>
> Ok, I have just found out that the setuid bit of "mpdroot" was set! After removing
> it, mpirun/mpdrun/mpiexec work as expected now :-) May be somebody can explain me
> why?
>
> Best regards,
> T.M. Tran