change current directory
disconnect and exit
Change escape key to ^X. Without argument, print current escape key
exit file transfer mode. ^D may also be used for this purpose.
|help||print help and tips|
|hook prg [args]||
Hook program prg on the the pty. Its standard input and output will go
through the ssh channel.
typing sz/rz is in fact equivalent to hook sz/hook rz
A weird imagination is most useful to gain full advantage of this feature.
same as exit.
repeats cmd forever (^C to interrupt). Useful for example if you use a
remote script invoking "sz" and you dont want to be typing "rz" each
Remember however that several files can be transferred by a single
sz/rz pair so this is not usually necessary to use repeat.
|rz||Receive files from the remote machine. runs rz and plugs the process on the ssh connection. running sz on the REMOTE machine is required :|
|1)||run sz <remote_file> ... from the remote machine shell|
|2)||press the escape sequence (C-space) to enter file transfer mode|
run the rz builtin
suspend zssh (back to the local machine shell)
|sz <file> ...||
Send files to the remote machine. runs sz and plugs the process on the ssh connection.
There is no need to manually run rz on the remote side.
print version information
builtins rz , sz , hook and exit return to shell mode after completion.
Do not ask user any question
-h --help show basic help
-s cmd --shell cmd run cmd as remote shell instead of the default "ssh -e none" (zssh) or "telnet -8 -E" (ztelnet)
ex: zssh -s "rsh -x"
-V --version show version
-z ^X --zssh-escape ^X set escape sequence to ^X
-- may be used to separate zssh options from ssh ones
Other arguments are passed verbatim to ssh/telnet/whatever.
ZSSHESCAPE Setting the ZSSHESCAPE environment variable allows to override the default escape sequence. ZSSHESCAPE should contain only two characters of the form ^X, meaning that ^X is to be the new escape sequence.
the following binaries need to be properly installed for zssh to work :
ssh/telnet/... the remote shell to be executed (local machine) sz rz zmodem send and receive programs. Should be both on local and remote machine, and (hopefully) of compatible versions.
If file transfer is initiated but never completes
( ie a line like :
Bytes Sent: 38144/4610624 BPS:3424 ETA 22:15
Bytes Sent: 0/ 513 BPS:0 ETA 00:00 Retry 0: Got ZCAN
can be seen, but transfer never completes
Chances are the pty/tty on one of the systems are not 8-bit clean. (Linux is 8-bit clean, NetBSD is not).
Using the -e (escape) option of rz should solve this problem.
Transfers can be interrupted with ^C (somewhat experimental =)
If you get stuck in rz/sz (for example youve just ran rz, but you then decided not to transmit anything), hit a dozen ^X (Ctrl-X, not the zssh escape!) to stop it
Use sz -y <files> to overwrite files on the other side
You may sometimes have to hit return 2 or 3 times after file transfer completion in order get back to the shell. Some digits are usually displayed; dont worry it wont harm (you or your term) ...
the tty may (sometimes) be somewhat upset after an interrupted transfer ( using ^C ). typing reset in this case should help.
no pipe, redirection (and other stuff) support in shell ... but after all there are already wonderful shells around =)
ttsshs author - Robert OCallahan - for the original idea
The sourceforge team.
Matthieu Lucotte <email@example.com>
zssh homepage: http://zssh.sourceforge.net
|ZSSH||ZSSH (1)||June 26, 2000|