As you see in the response, ksh can't find rsync (ksh: rsync: not found), and this is
included in the error stream of rsync (rsync: connection unexpectedly closed (0 bytes
read so far)). This means rsync is trying to run rsync, which means that you're using
external transport (single-colon (:) syntax). If by "trying to connect to a rsync
server" you mean "connect to a server using rsync over external transport", you
just need to make it possible for your local rsync to find the rsync
binary on that server. There are several ways to do that. Change the
global path on the remote system to include the location where the rsync
binary is kept, copy or link said binary somewhere into the path or put a
wrapper script named rsync in the path which just invokes the real one
with the same args (a symlink is better), or, least intrusively, use
'--rsync-path='.
If, in fact, you do have a rsync server running on the remote host, and
you want to contact that, use double colons '::' to seperate the hostname
from the module name. The rsync manpage covers these, and other
rsync-related topics in exquisite detail.
Tim Conway
[EMAIL PROTECTED]
303.682.4917
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e 'print pack(nnnnnnnnnnnn,
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970),
".\n" '
"There are some who call me.... Tim?"
"Victor J. Hernandez Gomez" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
01/22/2002 10:21 AM
To: [EMAIL PROTECTED]
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject: error in rsync protocol data stream (code 12) at io.c(139)
Classification:
When trying to connect to a rsync server (sparc.solaris.2.6) from a
linux machine (redhat 6.2).
# rsync machine.upo.es
ksh: rsync: not found
rsync: connection unexpectedly closed (0 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(139)
Both machines have 2.5.1 version of rsync code, compiled from scratch.
rsh is working
properly when rsync is not in scene.
Thank you in advance for your help,
--
Víctor Hernández
Centro de Informática y Comunicaciones
Universidad Pablo de Olavide, de Sevilla
