The first command is transferring the file and the second is not,
because the file has already been transferred. That's why the first
command is taking longer. What did you expect to see?
--
Matt
Thanks for your patience, Matt.
But when I change the user rights on this file with chmod
On Tue, 2009-02-03 at 14:46 +0100, David de Lama wrote:
The first command is transferring the file and the second is not,
because the file has already been transferred. That's why the first
command is taking longer. What did you expect to see?
--
Matt
Thanks for your patience,
But the strange thing with the timestamps is still disturbing me.
I deleted the cache as Sven told me with a bash file:
sync
echo 3 /proc/sys/vm/drop_caches
Did you do this between EVERY step below?
After creating a file of 1GB I copy it with the standard rsync command.
Then I made
On Thu, 2009-01-29 at 09:43 +0100, David de Lama wrote:
YES, the same results! The copy command takes nearly twice as long as the -c
command!:(
I can't explain it!!!
With the copy command I get following result:
receiving incremental file list
Thanks a lot guys!
I tested several files with the compression option and the compress level.
But the strange thing with the timestamps is still disturbing me.
I deleted the cache as Sven told me with a bash file:
sync
echo 3 /proc/sys/vm/drop_caches
After creating a file of 1GB I copy it
On Wed 28 Jan 2009, David de Lama wrote:
But the strange thing with the timestamps is still disturbing me.
I deleted the cache as Sven told me with a bash file:
sync
echo 3 /proc/sys/vm/drop_caches
Did you do this between EVERY step below?
After creating a file of 1GB I copy it with
On Wed, Jan 28, 2009 at 12:35:05PM +0100, David de Lama wrote:
rsync -acv --bwlimit=1 --stats --progress --delete
192.168.222.82:/home/test /backup/rsync0
Now it takes only about 45sec.
So I am still wondering. Am I doing s.th. wrong?!
The -c option tells rsync to read the source file
Hi @all!
Sorry about that many questions, but after searching and reading tons different
web sites, I didn't find exactly what I am searching for.
So, I know that with the -z Option rsync compresses the files with gzip, than
the files are transfared and at the target machine uncompressed.
I
On Tue 27 Jan 2009, David de Lama wrote:
So, I know that with the -z Option rsync compresses the files with gzip, than
the files are transfared and at the target machine uncompressed.
No, the data over the wire is compressed with the -z option; not the
file.
I made a test and transfered a
On Tue 27 Jan 2009, Paul Slootman wrote:
No, the data over the wire is compressed with the -z option; not the
file.
Correction: more specifically, the data between the sender and the
receiver processes is compressed.
Unfortunately this also happens when the transfer is local and -z
happens to
On Tue, 2009-01-27 at 14:49 +0100, Paul Slootman wrote:
Unfortunately this also happens when the transfer is local and -z
happens to be passed as an option; the result is that the transfer is
slowed down significantly without any benefit at all. Rsync should
perhaps give a warning about the
@Paul:
Yes, I ran sync on both machines. The same results! :(
@Matt:
I want to test it local, but how can I do it? I don't see the amount of data
rsync do compress.
___
NUR NOCH BIS 31.01.! WEB.DE FreeDSL - Telefonanschluss +
Tue, 27 Jan 2009 15:17:15 +0100, david.delama wrote:
Yes, I ran sync on both machines. The same results! :(
sync is not enough. You will need to call a script
dropcaches.sh that should contain (at least?):
-
# dropcaches.sh
# deletes
Tue, 27 Jan 2009 15:17:15 +0100, david.delama wrote:
I want to test it local, but how can I do it?
I don't see the amount of data rsync do compress.
-v should do.
Example:
rsync -z -v gcc-4.3.3.tar a
gcc-4.3.3.tar
sent 78,192,949 bytes received 31 bytes 3,191,550.20 bytes/sec
total size is
On Tue, 2009-01-27 at 15:17 +0100, David de Lama wrote:
I don't see the amount of data rsync do compress.
Use the %b log escape (see the rsyncd.conf(5) man page) to see the
amount of data actually sent over the wire to transfer each file.
Example:
$ rsync -r -z --out-format='%10b %10l %n'
On 27-Jan-2009, at 06:49, Paul Slootman wrote:
On Tue 27 Jan 2009, Paul Slootman wrote:
No, the data over the wire is compressed with the -z option; not the
file.
Correction: more specifically, the data between the sender and the
receiver processes is compressed.
Unfortunately this also
16 matches
Mail list logo
