Update: WARNING: --rsh or -e option ignored when connecting to rsync
daemon]
tim.conway at philips.com
tim.conway at philips.com
Mon Apr 15 08:58:02 EST 2002
You'll have to choose between transports. You are using the double-colon
(::) syntax, which specifies that rsync is to connect to a rsync daemon
running on port 873 (unless you specify a different port with --port=),
making its own tcp connection, rather than using an external transport
like rsh or ssh, thus the "-e ssh" part of your command is meaningless,
and rsync tells you so. From the output of your commands, it's apparent
that you have not set up a rsync daemon on the remote system. As ssh
works, you can simply use the standard single-colon syntax, which will
have rsync use an external transport, either the default, or the one you
specify via -e.
The developers have provided a very useful resource for answering such
questions, which is included in most methods of distributing rsync. Here's
a relevant excerpt:
There are six different ways of using rsync. They are:
SunOS 5.7 Last change: 29 May 2001 1
User Commands rsync(1)
o for copying local files. This is invoked when neither
source nor destination path contains a : separator
o for copying from the local machine to a remote machine
using a remote shell program as the transport (such as
rsh or ssh). This is invoked when the destination path
contains a single : separator.
o for copying from a remote machine to the local machine
using a remote shell program. This is invoked when the
source contains a : separator.
o for copying from a remote rsync server to the local
machine. This is invoked when the source path contains
a :: separator or a rsync:// URL.
o for copying from the local machine to a remote rsync
server. This is invoked when the destination path con-
tains a :: separator.
o for listing files on a remote machine. This is done the
same way as rsync transfers except that you leave off
the local destination.
Note that in all cases (other than listing) at least one of
the source and destination paths must be local.
SETUP
See the file README for installation instructions.
Tim Conway
tim.conway at philips.com
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?"
Jack Khoo <jackkhoo at xybase.com>
Sent by: rsync-admin at lists.samba.org
04/14/2002 10:38 PM
To: rsync at samba.org
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject: Update: WARNING: --rsh or -e option ignored when connecting to rsync
daemon]
Classification:
UPDATE
i able to ssh between this 2 remote server, below is the extra info
rsync -avue ssh . username at hostname::sharefolder
WARNING: --rsh or -e option ignored when connecting to rsync daemon
rsync: failed to connect to HOSTNAME: Connection timed out
rsync error: error in socket IO (code 10) at clientserver.c(89)
----- Message from Jack Khoo <jackkhoo at xybase.com> on Mon, 15 Apr 2002
12:22:49 +0800 -----
To:
rsync at samba.org
Subject:
WARNING: --rsh or -e option ignored when connecting to rsync daemon
i faced a problem as below :
WARNING: --rsh or -e option ignored when connecting to rsync daemon
when i trying to sync between 2 remote server, Sun 2.8 and AIX 4.3.3
Sun Rsync - 2.5.4
AIX Rsync - 2.4.5
isn't ok for this 2 different version of rsync to communicate each
others,
don't it affect by ssh daemon/version as well
kindly advise
--
To unsubscribe or change options:
http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
More information about the rsync
mailing list