Re: GNU Parallel Bug Reports --ssh 'autossh' not working and --ssh 'autossh -M {PORT} not expanded

[Marco Tamassia]

I think that Ole wanted the --ssh argument to be applied both to ssh and rsync invocations. You are saying that the longer and possibly non-interactive connections are those by ssh rather than rsync. I find your point valid, but I see why Ole would like the --ssh mechanism to be more general. Furthermore, if the --ssh argument is already being used for rsync, changing this behaviour would break retro-compatibility.

Anyway, after what I hear about autossh I went looking for alternatives. I found about mosh, and I will test it in the next days.

This aside, my first email I was reporting a second bug. Is that fixable? Even though I cannot think of other use cases for it, it seems to me that parameters expansion should be applied to all of parallel arguments (there may be exceptions, though). What do you guys think?

On 23 September 2015 at 15:05, Andreas Bernauer <address@hidden> wrote:

On 23/09/15 1:11, Ole Tange wrote:
> On Tue, Sep 22, 2015 at 11:09 PM, Andreas Bernauer
> <address@hidden> wrote:
> :
>> Thus, another solution is that parallel tells ssh to stop parsing
>> options with '--':
>> ssh localhost -- perl -e \'"print 1"\'
>>
>
> How do you do that for rsync (which is used for file transfer)?
>
>     rsync -e ssh ... [something with -e and and stuff]
>
> I do not see a way of providing rsync with a template in which to put
> the hostname with -- appended:

I've just checked the rsync sources and rsync appends the host name to
the command given with -e. I don't see a way to add arguments after the
hostname.

I was wondering why you'd need '[something with -e and and stuff]' for
the ssh command to rsync, as I don't know parallel's internals. I would
have expected that rsync is used to transfer the files (with an ssh that
does not need '--' or '[something with -e and and stuff]') and then a
separate ssh command starts the remote command (which would need the '--').

> Also it seems autossh ignores exit code

That's a no-go.

-Andreas

--

Marco Tamassia