Hi there,
> I upgraded to lsh-2.0 today, and now lsftp doesn't work :-/ Is it just
> me? I've tried it against all manner of servers and it always fails...
>
> # lsftp <hostname> -- 'cd /tmp'
> Broken pipe
>
> Actually, the same thing happens even if I make up some bogus value for
> the hostname so it doesn't appear to be a compatibility issue.
lsftp typically runs lshg -G <whatever you send to lsftp before --> to
set up a connection, so you might want to try to see if that works.
You might also try pre-establishing a gateway (with lsh -G -N -B hostname
or something like that) or using another program for transport (setting
LSFTP_RSH to your lsh).
I think the problem you describe could occur if there's no gateway
available and lshg doesn't find you lsh to fall back on (lsh not in
PATH).
HTH
/Pontus
--
Pontus Freyhult, see <URL:http://soua.net/> for more information.
_______________________________________________
lsh-bugs mailing list
[EMAIL PROTECTED]
http://lists.lysator.liu.se/mailman/listinfo/lsh-bugs
