From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: rsync 3.2.0
Date: Sat, 20 Jun 2020 17:09:07 +0200 [thread overview]
Message-ID: <8ed12d36-925a-7dbb-7ed6-9d37ea5dfa81@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
Hi,
rsync 3.2.0 is out and I just had time...for details see:
https://download.samba.org/pub/rsync/src/rsync-3.2.0-NEWS
Right now running under Core 145 / x86_64. No problems.
But I still have two questions.
In order to use the new xxhash checksum support and zstd compression,
the corresponding kernel modules would need to be activated. Do we want
or need these?
For now, I disabled both with these configure options:
...
--disable-xxhash \
--disable-zstd
...
Do we want (would someone use) the new 'rsync-ssl'-script? On a firewall!?
Current capabilities:
***SNIP***
root(a)ipfire: /tmp # ./rsync --version
rsync version 3.2.0 protocol version 31
Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints,
socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append,
ACLs, xattrs, iconv, symtimes, prealloc, SIMD
Checksum list:
md5 md4 none
Compress list:
lz4 zlibx zlib none
***SNAP***
Best,
Matthias
next reply other threads:[~2020-06-20 15:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 15:09 Matthias Fischer [this message]
2020-06-25 8:54 ` Michael Tremer
2020-06-25 15:28 ` Matthias Fischer
2020-06-25 15:35 ` Michael Tremer
2020-06-25 15:56 ` Matthias Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8ed12d36-925a-7dbb-7ed6-9d37ea5dfa81@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox