On May 3, 2010, at 1:32 PM, Ralph Castain wrote:
> I believe the intent of the (test...) was to see if a .profile existed and
> execute that if so. This was at the request of users who complained that
> their remote environment wasn't being setup as expected when we launched
> their jobs.
I believe the intent of the (test...) was to see if a .profile existed and
execute that if so. This was at the request of users who complained that their
remote environment wasn't being setup as expected when we launched their jobs.
Might be a better way to do it, though...
On May 3, 2010, at
Hello,
* Jeff Squyres wrote on Mon, May 03, 2010 at 04:04:59PM CEST:
> > On Apr 29, 2010, at 11:24 AM, Jonathan Vincent wrote:
> >
> > > sh -c '/usr/bin/env FOO=bar (echo hello)'
> > > ksh -c '/usr/bin/env FOO=bar (echo hello)'
> > >
> > > is not valid
> > > sh -c '/usr/bin/env FOO=bar echo
FWIW, I filed https://svn.open-mpi.org/trac/ompi/ticket/2400 about this issue.
On May 3, 2010, at 9:04 AM, Jeff Squyres (jsquyres) wrote:
> On Apr 29, 2010, at 11:24 AM, Jonathan Vincent wrote:
>
> > i.e. a simpler version such as
> >
> > sh -c '/usr/bin/env FOO=bar (echo hello)'
> > ksh -c
On Apr 29, 2010, at 11:24 AM, Jonathan Vincent wrote:
> i.e. a simpler version such as
>
> sh -c '/usr/bin/env FOO=bar (echo hello)'
> ksh -c '/usr/bin/env FOO=bar (echo hello)'
>
> is not valid
> sh -c '/usr/bin/env FOO=bar echo hello'
> works.
Per your later mails, plm_rsh_module.c does
Thanks Jon.
I fear this falls into the "won't fix until I have some spare time" category -
probably won't get to it myself until Aug/Sept due to priorities.
In the interim, perhaps someone who has more priority in this area will step in
to fix it.
On Apr 30, 2010, at 3:15 PM, Jonathan
Hi,
The code path is used when the user has /bin/sh as their login shell.
There seemed to be seperate code paths depending on the login shell. I
guess it is not suprising noone has looked at this part for a long
time, /bin/sh is not a popular choice :D. It *should* be easily
reproduceable if you
Can you pinpoint where you think the logic is incorrect? I can't easily see
where the parens are being added, and don't know anyone who checks/uses that
code path.
This hasn't been touched in a very long time, which makes me a tad cautious in
how this gets changed. Would need someone to either
