Re: [OMPI users] problem calling mpirun from script invoked with mpirun

Thanks, That's what I wanted to know. And thanks for all the help! Luke On Wed, Oct 28, 2009 at 9:06 PM, Ralph Castain wrote: > I see. No, we don't copy your envars and ship them to remote nodes. Simple > reason is that we don't know which ones we can safely move, and which

Re: [OMPI users] problem calling mpirun from script invoked with mpirun

I see. No, we don't copy your envars and ship them to remote nodes. Simple reason is that we don't know which ones we can safely move, and which would cause problems. However, we do provide a mechanism for you to tell us which envars to move. Just add: -x LD_LIBRARY_PATH to your mpirun cmd line

Re: [OMPI users] problem calling mpirun from script invoked with mpirun

My apologies for not being clear. These variables are set in my environment, they just are not published to the other nodes in the cluster when the jobs are run through the scheduler. At the moment, even though I can use mpirun to run jobs locally on the head node without touching my

Re: [OMPI users] problem calling mpirun from script invoked with mpirun

Normally, one does simply set the ld_library_path in your environment to point to the right thing. Alternatively, you could configure OMPI with --enable-mpirun-prefix-by-default This tells OMPI to automatically add the prefix you configured the system with to your ld_library_path and path

Re: [OMPI users] problem calling mpirun from script invoked with mpirun

Thanks for the quick reply. This leads me to another issue I have been having with openmpi as it relates to sge. The "tight integration" works where I do not have to give mpirun a hostfile when I use the scheduler, but it does not seem to be passing on my environment variables. Specifically

Re: [OMPI users] problem calling mpirun from script invoked with mpirun

I'm afraid we have never really supported this kind of nested invocations of mpirun. If it works with any version of OMPI, it is totally a fluke - it might work one time, and then fail the next. The problem is that we pass envars to the launched processes to control their behavior, and these