[Swift-devel] command line ssh provider...

[Michael Wilde]

I think the reason this fixed the ssh problem is that the SSH_AUTH_SOCK etc vars were getting erased at step 1, and this fix stopped these local env vars from getting lost, right?

- Mike

----- Original Message -----
> From: "Jonathan Monette" <jonmon at mcs.anl.gov>
> To: "Mihael Hategan" <hategan at mcs.anl.gov>
> Cc: "Swift Devel" <swift-devel at ci.uchicago.edu>
> Sent: Tuesday, January 17, 2012 5:17:44 PM
> Subject: Re: [Swift-devel] command line ssh provider...
> Ok. I understand now. Anyways the switch to ProcessBuilder fixed the
> issue.
> 
> On Jan 17, 2012, at 5:12 PM, Mihael Hategan wrote:
> 
> > On Tue, 2012-01-17 at 17:08 -0600, Jonathan Monette wrote:
> >>> Though now that I think about it, this wasn't strictly necessary
> >>> since
> >>> for the ssh-cl provider, the task environment variables shouldn't
> >>> be
> >>> passed to the ssh subprocess (they go on the command line of the
> >>> ssh
> >>> shell).
> >> What do you mean by this? When I saw the command line of the ssh
> >> shell no environment variables are being passed.
> >
> > 1. java forks ssh
> > 2. ssh -> sshd
> > 3. sshd forks shell
> >
> > There is no point in passing task env vars in (1). You need them
> > somewhere in (3).
> >
> > You don't see them in the shell command line because they are passed
> > on
> > its stdin (i.e. as if typed).
> >
> 
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel

-- 
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory