Thanks Alan. However, I don't know how to achieve that (change the ssh
command so that it starts a bash shell).
In fact, I was surprise that when I login as root (which has bash as its
login shell) the same problem persists.
On Sat, Oct 5, 2013 at 1:58 AM, Alan Schmitt <alan.schm...@polytechnique.org
> wrote:
> Hello,
>
> This is very interesting, I just stumbled upon sshuttle a few days ago
> (following a link on twitter).
>
> wypon...@gmail.com writes:
>
> > Has anyone been using sshuttle with fish.
> > I ran into the following troubles.
> >
> > fish: Unknown command “P=python2”. Did you mean “set P python2”? For
> > information on assigning values to variables, see the help section on the
> > set command by typing “help set”.
> > Standard input: P=python2; $P -V 2>/dev/null || P=python; exec "$P" -c
> > 'import sys; skip_imports=1; verbosity=2; exec
> compile(sys.stdin.read(764),
> > "assembler.py", "exec")'
> > ^
> > fish: Variables may not be used as commands. Instead, define a function.
> > See the help section for the function command by typing “help function”.
> > Standard input: P=python2; $P -V 2>/dev/null || P=python; exec "$P" -c
> > 'import sys; skip_imports=1; verbosity=2; exec
> compile(sys.stdin.read(764),
> > "assembler.py", "exec")'
> > ^
> > fish: Expected a command name, got token of type “Pipe”. Did you mean
> > “COMMAND; or COMMAND”? See the help section for the “or” builtin command
> by
> > typing “help or”.
> > Standard input: P=python2; $P -V 2>/dev/null || P=python; exec "$P" -c
> > 'import sys; skip_imports=1; verbosity=2; exec
> compile(sys.stdin.read(764),
> > "assembler.py", "exec")'
> > ^
> > c : fatal: server died with error code 127
> > -----------------------------------------------------------
> >
> > I guess the codes were written with bash shell in mind.
> > Cos I can run sshuttle without a problem on a bash shell.
>
> I can run sshuttle with no issue when the client is a fish shell. I
> guess the problem in your case is that the server is also a fish
> shell. If it's possible to change the ssh command so that it starts a
> bash shell instead of fish, this sshuttle option might be of interest:
>
> ,----
> | -e, --ssh-cmd
> | : the command to use to connect to the remote server. The
> | default is just `ssh`. Use this if your ssh client is
> | in a non-standard location or you want to provide extra
> | options to the ssh command, for example, `-e 'ssh -v'`.
> `----
>
> Alan
>
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
Fish-users mailing list
Fish-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fish-users
