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

[Ole Tange]

On Wed, Sep 23, 2015 at 7:41 AM, Marco Tamassia
<address@hidden> wrote:
> I think that Ole wanted the --ssh argument to be applied both to ssh and
> rsync invocations.

This is how GNU Parallel works internally: The ssh command used for
running a command is also the ssh command used for rsync. The reason
being that you might simply be giving full path to ssh which might not
otherwise be in your path, or you might use a special version of ssh
that runs over TOR or some other fancy stuff.

> 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.

I have used mosh for around a year now.

+ It works really well if you change IP-address (e.g. take your laptop
from home to work and continue working).
- Like autossh the arguments sent to the remote system cannot contain
anything that can be mistaken for an option:
   mosh localhost ls -l # Fails, because -l is not a mosh option (stupid)
   mosh localhost -- ls -l # Works
- It only keeps your (ncurses) screen up to date. So no scroll buffer
and absolutely no transfer of stdout/stderr.
- Exit code is ignored

The last 2 make mosh pretty much useless for GNU Parallel.

Why do you not like ssh? Can -oServerAliveInterval=60 help you from
losing your connections?


/Ole