Thank you very much for your valuable suggestions.
Now I am able to mirror the set of files from one system to another system which are on the net.
Yesterday, I calculated it is mirroring 188MB
file in 63 sec from one side to another side.
Good performance. Is anywhere the performance about
rsync is mentioned in terms of file size / time.
I am going to use this rsync command in script continously to mirror the two systems always.
Once again thanks,
regards,
laks
[EMAIL PROTECTED] wrote:
I just played back your mail in my head, and realized that you mentioned
the rsync server. I read your command, from which it was plain that you
were NOT trying to contact a rsync server, and gave instructions based on
that. In case you were trying to contact a rsync server (rsyncd), I
suggest you read the man pages for both rsync and rsyncd.conf. the rsync
manpage explains how to invoke rsync to have it be a server, and the
rsyncd.conf manpage explains how to set up the required configuration
file. The rsync manpage also explains how to invoke rsync to CALL a
server (as opposed to starting a temporary process via an external
transport to act as your remote server, as your commandline showed).
Direct consultation of the documentation which Tridge, Martin, Dave, and
everybody else has put so much work into, can cover the broad
possibilities with much less latency than an email list.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?"Tim Conway
02/04/2002 08:33 AMTo: [EMAIL PROTECTED]
cc: Lakshminarayanan Radhakrishnan <[EMAIL PROTECTED]>
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Subject: Re: Doubt in Rsync !!
Classification: UnclassifiedOk: You're using an external transport (rsh, unless you've defined
RSYNC_RSH as something else(probably ssh)). First thing to check is
whether you can rsh to destinationmachine. See what happens if you do
"rsh destinationmachine uname -a". Does this report back the information
for destinationmachine, or does it give you "Permission denied". If so,
get rsh working. From your error, I'm certain this is the problem, as if
it were a permission problem on a file or directory, you'd get an error
more like this
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
tconway@atlas
/site/local/share/ToolSync/newsync>rsync newsync.log.2 atlas:/kernel
mkstemp .newsync.log.2.GYaiMq failed
rsync error: partial transfer (code 23) at main.c(537)
tconway@atlas
/site/local/share/ToolSync/newsync>
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-- -----------------R.Lakshminarayanan -----------------Axes Technologies India Pvt. Ltd., -----------------Chennai - 600 034. -----------------Email : [EMAIL PROTECTED], Phone: 8253323