2000-07-10-07:01:21 AFRIZAL-IPTN:
> rync italbsgi1:file_name.txt file.txt
> I got message like this
> rsync: ERROR: Illegal option -- -
> usage: rsync [-c command] [-r rcsdir] [-Rv]
> [dirname ...]
> unexpected EOF in read_timeout
The syntax error message doesn't look like it comes from the rsync
we're here to talk about, the one for copying files efficiently over
network connections. Looks like some helper script for RCS maybe?
However, the "unexpected EOF in read_timeout" certainly does. So
you're running the right rsync locally, and the wrong one remotely.
When you run rsync to or from a remote file like this, it invokes
rsh(1) (can be overriden with "-e" or the RSYNC_RSH environment
variable) to connect to the more system. It looks like that's
working.
The actual rsh (or ssh, or whatever transport you've requested)
command ends up looking something like
rsync --server ...
with a bunch of options that tells the remote rsync what its part of
the job will be. _That_ part seems to be what's failing.
I'd guess if you ran the command
rsh italbsgi1 which rsync
you'd discover you're invoking the wrong rsync there. Find where the
right rsync is located and make sure you invoke it; install your own
if necessary (can be a copy of the local rsync executable if the
machines are the same OS and architecture). You can control what
path is used to invoke rsync on the remote end with the --rsync-path
option. E.g. if you've copied rsync into your home dir/bin on the
remote end, and your home dir on that remote system is
/home/afrizal, then you might be able to use
rsync --rsync-path=/home/afrizal/bin/rsync \
italbsgi1:file_name.txt file.txt
-Bennett
PGP signature
