ssh is version 2.9. RedHat 7.1. I try to keep the latest updates, but
sometimes I get behind.
- Original Message -
From: Dave Dykstra [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, November 14, 2001 5:02 PM
Subject: Re: rsync: Re: using rsync to backup windows workstations
I'll just use scp. It's faster using virtually the same method.
scp remote:`find /home/www/html/ -maxdepth 1 -name
*.[j,g,h][pg,if,tml]* -type f` /home/www/html 21
On Thu, Nov 15, 2001 at 07:42:18AM +0100, Ph. Marek thus spat:
| It is a reiserfs system on the client, and ext2 on the rsync
On Thu, Nov 15, 2001 at 09:42:53AM +0800, Michael P. Carel wrote:
I'm using RedHat 6.1 and the latest rsync rpm package. I've adding or
incresing its verbosity by having a triple v :
rsync -acvvv --progress --stats --timeout=0 host::shared path
It does start downloading the file and
Here is a newbie question. Hope, you will not mind.
I am trying to backup a file from my NT machine onto AIX machine. Here
is the setup:
NT machine (testor): rsync is in c:\Rsync\rsync.exe and is running as a
daemon. (I created a service for Rsync first).
AIX machine (admx): rsync -v
rsync
What is the default block size? I have a few
files 30+mb and data is just added to the end of them. It seems like it
takes longer to sync them that it was to send it initially. Should I
change the block size or something else? I am running:
rsync -z -e ssh *.* user@linuxbox:data/
I need to
You'll have to chose between the external transport via ssh and the rsync daemon. The commandline to use the rsyncd, based on your example, would be
rsync -v guest@testor::c:/Temp/pix.log .
I'm guessing, however, that you don't have a module named c: in your rsyncd.conf.
I would hope that
Thomas Lambert [[EMAIL PROTECTED]] writes:
What is the default block size? I have a few files 30+mb and data
is just added to the end of them. It seems like it takes longer to
sync them that it was to send it initially. Should I change the
block size or something else?
The default is an
(I previously wrote)
So your 30MB file ought to be using 16K blocks
Whoops - my fault for assuming 30MB was large enough and skipping the
calculations. Turns out that really only yields about a 3K block size
with the adaptive algorithm. So you can get significant reduction in
blocks by using
I want to send a subset of directories sepcified in include arguments
to a client, but I am creating all the
peer and parent directories as well, although they are empty - here is
basically what I'm doing.
assuming I have /staging/upgrade/dir1, /staging/upgrade/dir2 and
/staging/upgrade/dir3 on
