Re: GNU Parallel Bug Reports why is parallel invoking a shell **by default** and associated bugs

[Stephane Chazelas]

2015-05-25 22:08:03 +0200, Ole Tange:
[...]

Thanks for the long reply and fixes. That argumentation of
yours makes a lot of sense.

> > - document limitations when using {} in some shell contexts.
> 
> I need help with that.

I'll see if I can help.

> > A feature that I would really welcome would be some --no-shell
> > option that skips all that business about running a shell and
> > building a correct command-line for it and just executes the
> > command (a bit like xargs).
> 
> If I receive a patch that does this, I will not rule this out.
[...]

I'd still find that useful. Though I suppose that's where I can
use gxargs -P instead.

I've just posted

http://unix.stackexchange.com/questions/205567/how-to-execute-an-arbitrary-simple-command-over-ssh-without-knowing-the-login-sh

that would help covering the --no-shell aspect over ssh (ssh
always invoking a shell is one of the things I find most
annoying about it, that and no easy way to kill the remote
command upon connection loss which you also ran into).

Even outside --no-shell, you may still find it useful to
abstract yourself from the user's login shell on the remote
host.

-- 
Stephane