-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rich Rauenzahn wrote:
>
>
> Les Mikesell wrote:
>> Adam Goryachev wrote:
>>
>>> In this case, it no longer matters, and for those that are interested in
>>> how to use rsync to transfer a 20G file full of 0's in a few minutes
>>> over a very slow
Les Mikesell wrote:
Adam Goryachev wrote:
In this case, it no longer matters, and for those that are interested in
how to use rsync to transfer a 20G file full of 0's in a few minutes
over a very slow connection, here is how:
rsync --partial --progress source destination
Then, cancel the t
Adam Goryachev wrote:
>
> In this case, it no longer matters, and for those that are interested in
> how to use rsync to transfer a 20G file full of 0's in a few minutes
> over a very slow connection, here is how:
>
> rsync --partial --progress source destination
> Then, cancel the transfer after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Craig Barratt wrote:
> Adam writes:
>
>> But now my backup is timeing out on this file, and it doesn't even run
>> long enough to backup this entire file, so it removes the file each time
>> it attempts to run the backup.
>
> What sort of timeout do
Adam writes:
> But now my backup is timeing out on this file, and it doesn't even run
> long enough to backup this entire file, so it removes the file each time
> it attempts to run the backup.
What sort of timeout do you get? If it is an ALARM signal you
should significantly increase $Conf{Clie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have backuppc doing backups of my remote system using rsync, which is
working well. Recently, I created a 10G file on the remote system like this:
dd if=/dev/zero of=file bs=1M count=10240
Or whatever, so the file is not a sparse file or anyth
