Kevin,
thanks so much, I should have read the man page closer:
--existing, --ignore-non-existing
This tells rsync to skip creating files (including directories) that do not
exist yet on the destination. If this option is combined with the
--ignore-existing option, no files will be updated (wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually, you want --delete --ignore-non-existing and --ignore-existing
On 02/16/12 20:55, Kevin Korb wrote:
> You want --ignore-existing
>
> On 02/16/12 20:36, Bryan Pliatsios wrote:
>> Hello all,
>
>> I thought --recursive and --delete-before m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You want --ignore-existing
On 02/16/12 20:36, Bryan Pliatsios wrote:
> Hello all,
>
> I thought --recursive and --delete-before might be an option and
> I can quit rsync when it begins the updates, but the incremental
> recursive scanning is disab
Hello all,
I thought --recursive and --delete-before might be an option and I can
quit rsync when it begins the updates, but the incremental recursive scanning
is disabled and this will certainly crash rsync as it was before moving to v3.x
(too many files).
I have no experience with -
AGH !
I postet the wrong checksums, I posted the ones for
cwRsync_4.2.0_Installer.zip instead of cwRsyncServer_4.2.0_Installer.zip
cwRsyncServer_4.2.0_Installer.zip:
MD5: c787dfa854775793d1a1b5c3502b57b5
SHA-256: 21e608caed9e5e7e1f1f9881729eab0a8fce6e1ff31d85dcb7759d502478160c
The checksums ar
A bit late, but someone (anonymous) provided a link to download.
the md5 is correct, it matches the last sourceforge state. And the md5
and sha256 mentioned at https://www.itefix.no/i2/node/12862 - before he
gave up the project.
MD5 c787dfa854775793d1a1b5c3502b57b5
sha256 5abeec588e937bd749456d
I've had an idea for a backup concept that could be new, or at least I
have not been able to find anything similar on the net. It's something
like a "reversed rsync", although this term is already commonly used for
"backup restoration".
The goal is to get the best of both pull and push backup meth
On Wed, Feb 15, 2012 at 6:21 AM, Carlos Carvalho wrote:
> filename overflows max-path len by 1:
>
Count the characters in the displayed and you'll see what the
max_path value is. That message is output by the sender, and indicates
names that are too long to put into the stream of file-list dat
