Re: malloc assert

2021-01-31 Thread Wayne Davison via rsync
On Wed, Jan 27, 2021 at 2:19 AM Hans Andersson wrote: > I occasionally get the following error when running rsync [malloc.c > assertion] > Since rsync doesn't supply any malloc code, that's probably a question for your C-library provider. You might first try out 3.2.3, which fixed a couple mem

Re: Bug when using rsync -r --delete -b --backup-dir

2021-01-15 Thread Wayne Davison via rsync
On Mon, Nov 23, 2020 at 1:33 PM CRTS via rsync wrote: > then the empty directory does end up in bkp. > You mean "does not". That is correct, as it only creates backup dirs to hold backup files. I recall this being specifically chosen as the desired outcome but not the details of why (since it

Re: Is there a default for 'pid file' for rsync in daemon mode?

2021-01-02 Thread Wayne Davison via rsync
On Fri, Jan 1, 2021 at 2:13 PM raf wrote: > maybe the pidfile should be locked > https://download.samba.org/pub/rsync/NEWS#3.2.0 ..wayne.. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options:

Re: Is there any way to restore/create hardlinks lost in incremental backups?

2020-12-13 Thread Wayne Davison via rsync
I should also mention that there are totally valid reasons why the dir might be huge on day4. For instance, if someone changed the mode on the files from 664 to 644 then the files cannot be hard-linked together even if the file's data is unchanged. The same goes for differences in preserved

Re: Is there any way to restore/create hardlinks lost in incremental backups?

2020-12-13 Thread Wayne Davison via rsync
You could rsync the current day4 dir to a day4.new dir, and list all the prior days as --link-dest options. Make sure that you're using the same xatt/acl options as your official backup command (the options may or may not be present) so that you are preserving the same level of info as the backup.

Re: A strange problem with my daily backups performed via rsync

2020-11-02 Thread Wayne Davison via rsync
On Mon, Nov 2, 2020 at 3:03 AM Manish Jain wrote: > rsync -av --delete src dst # but protect dir dst/XYZ from deletion > > I tried "--filter 'protect dst/XYZ'" but that does not prevent the > directory dst/XYZ from being deleted. > The "dst" dir isn't in the transfer, so it can't appear in a

Re: Syncing multiple sub-directories to one directory

2020-09-30 Thread Wayne Davison via rsync
On Tue, Sep 29, 2020 at 4:46 PM Rob Campbell wrote: > Thanks for your help. What you provided didn't work for me because that > still placed things in subdirectories. > Ah, that's what you were trying to do. Your original email sounded like you just didn't want it to recurse into

Re: strange crash with md5p8.diff + xxhash

2020-09-29 Thread Wayne Davison via rsync
On Sun, Sep 27, 2020 at 9:01 AM Madhu via rsync wrote: > Turns out the comment in rsync.h: (struct name_num_obj): > struct name_num_item list[8]; /* A big-enough len (we'll get a > compile error if it is ever too small) */ > > isn't correct. I don't get a compile error. Gcc likes to

Re: rsync 3.1.3 dry run bug?

2020-09-29 Thread Wayne Davison via rsync
On Sun, Sep 27, 2020 at 12:27 PM Dipl.-Ing. Wolf-Dieter Pichler wrote: > In this example output rsync says that it would just perform two > group changes, BUT despite the -n option it actually synced some documents. > I doubt that very much, so I'd suggest checking on what else might be going

Re: Syncing multiple sub-directories to one directory

2020-09-29 Thread Wayne Davison via rsync
On Tue, Sep 29, 2020 at 7:38 AM Rob Campbell wrote: > I would like to sync many subdirectories into one directory with no > subdirectories. I've tried > > rsync -rv --progress --include '*.jp*g' --include '*.png' --include > '*.dng' --include '*.raw' --include '*.nef' --include 'Duo' --include >

Re: Skip source files that differ from existing destination files with a warning?

2020-09-23 Thread Wayne Davison via rsync
On Thu, Sep 17, 2020 at 5:32 AM Matt McCutchen wrote: > For the "not transfer" part, I can use --ignore-existing, but I don't see > a direct way to be warned only about source files that differ from > existing destination files. > Indeed, the 2-step approach that you mentioned is all that the

Re: Security issue: How to report it privately to the maintainers?

2020-09-02 Thread Wayne Davison via rsync
On Tue, Sep 1, 2020 at 8:43 PM Philippe Höij wrote: > There is a security issue in rsync that needs to be disclosed to the team. > I added a security policy to the repo which indicates that security issues can be emailed to me. ..wayne.. -- Please use reply-all for most replies to avoid

Re: Rsync 3.2.3 released

2020-08-07 Thread Wayne Davison via rsync
On Thu, Aug 6, 2020 at 10:46 PM Rupert Gallagher wrote: > I noted that rsync writes a gmon file on the source path and leaves it > there when it terminates. Nope, it doesn't. You'll need to figure out what's going on with your setup. Also, I have 12GB of cache in ecc ram that rsync is not

Re: Rsync 3.2.3 released

2020-08-07 Thread Wayne Davison via rsync
On Thu, Aug 6, 2020 at 11:48 PM Michal Ruprich wrote: > I see that a couple of patches from the rsync-patches tar have > disappeared, like acls.diff or xattrs.diff yet I don't see the changes in > the code. Is there a reason for their removal? > Various things were removed that had limited value

[rsync-announce] Rsync 3.2.3 released

2020-08-06 Thread Wayne Davison via rsync-announce
I have released rsync 3.2.3. It contains a smattering of bug fixes and various enhancements. To see a summary of all the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS#3.2.3 You can download the source tar file and its signature from here:

Rsync 3.2.3 released

2020-08-06 Thread Wayne Davison via rsync
I have released rsync 3.2.3. It contains a smattering of bug fixes and various enhancements. To see a summary of all the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS#3.2.3 You can download the source tar file and its signature from here:

Re: Rsync 3.2.3pre1 released

2020-07-29 Thread Wayne Davison via rsync
On Tue, Jul 28, 2020 at 4:43 PM Nelson H. F. Beebe via rsync < rsync@lists.samba.org> wrote: > xxhash in particular is not a package that we have needed before, so none > of the clients has it. > All new, wonderful libraries have a point in time where they begin to get used. If you transfer

[rsync-announce] Rsync 3.2.3pre1 released

2020-07-27 Thread Wayne Davison via rsync-announce
have made rsync 3.2.3pre1 available for release testing. This combines some bug fixing with a good chunk of enhancements. To see a summary of the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS You can download the source tar file and its signature from here:

Rsync 3.2.3pre1 released

2020-07-27 Thread Wayne Davison via rsync
have made rsync 3.2.3pre1 available for release testing. This combines some bug fixing with a good chunk of enhancements. To see a summary of the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS You can download the source tar file and its signature from here:

Re: Syncing from two sources to one target and deleting files not in either source

2020-07-21 Thread Wayne Davison via rsync
On Tue, Jul 21, 2020 at 4:15 AM @lbutlr wrote: > how can I remove files on Server 3 that do not exist on either Server 1 or > Server 2? > If you want rsync to do the deletions during a copy from one of the servers, you'll need a filter file of "protect" (P) rules for every dir and file on the

Re: --exclude vs --filter

2020-07-11 Thread Wayne Davison via rsync
On Sat, Jul 11, 2020 at 12:59 AM Roland wrote: > can "--filter" statements completely replace "--exclude" statements Yes. The old-style exclude/include options just turn into the simplest form of exclude/include filter rules. ..wayne.. -- Please use reply-all for most replies to avoid

[rsync-announce] Rsync 3.2.2 released

2020-07-05 Thread Wayne Davison via rsync-announce
I have released rsync 3.2.2. This is a few more portability fixes, some improvements to the newest features, and some other simple changes. Hopefully this will be the last of these recent touch-up releases. To see a summary of all the recent changes, visit this link:

Rsync 3.2.2 released

2020-07-05 Thread Wayne Davison via rsync
I have released rsync 3.2.2. This is a few more portability fixes, some improvements to the newest features, and some other simple changes. Hopefully this will be the last of these recent touch-up releases. To see a summary of all the recent changes, visit this link:

[rsync-announce] Rsync 3.2.2pre3 released

2020-07-01 Thread Wayne Davison via rsync-announce
I have made rsync 3.2.2pre3 available for release testing. This release has a fix for a crash that affects some daemon setups. I also took the opportunity to make the daemon parameters configuration simpler to keep all the define/init/access bits in sync. To see a summary of the recent changes,

Rsync 3.2.2pre3 released

2020-07-01 Thread Wayne Davison via rsync
I have made rsync 3.2.2pre3 available for release testing. This release has a fix for a crash that affects some daemon setups. I also took the opportunity to make the daemon parameters configuration simpler to keep all the define/init/access bits in sync. To see a summary of the recent changes,

[rsync-announce] Rsync 3.2.2pre2 released

2020-06-28 Thread Wayne Davison via rsync-announce
I have made rsync 3.2.2pre2 available for release testing. I noticed a couple more minor issues with building from an alternative dir, so I simplified the build-dir idiom to put all the generated files in the build dir instead of having some of the configure-related ones in the src dir. This

Rsync 3.2.2pre2 released

2020-06-28 Thread Wayne Davison via rsync
I have made rsync 3.2.2pre2 available for release testing. I noticed a couple more minor issues with building from an alternative dir, so I simplified the build-dir idiom to put all the generated files in the build dir instead of having some of the configure-related ones in the src dir. This

[rsync-announce] Rsync 3.2.2pre1 released

2020-06-27 Thread Wayne Davison via rsync-announce
I have made rsync 3.2.2pre1 available for release testing. This is a few more portability fixes, some improvements to the newest features, and a couple other simple changes. If no blocking issues are found, this will be released as 3.2.2 soon. At that point I imagine that this will be the last of

Rsync 3.2.2pre1 released

2020-06-27 Thread Wayne Davison via rsync
I have made rsync 3.2.2pre1 available for release testing. This is a few more portability fixes, some improvements to the newest features, and a couple other simple changes. If no blocking issues are found, this will be released as 3.2.2 soon. At that point I imagine that this will be the last of

Re: Rsync Daemon Remote Pull

2020-06-27 Thread Wayne Davison via rsync
On Sat, Jun 27, 2020 at 7:17 AM Chandrasekar Natarajan wrote: > Kindly help me to resolve this. > One thing you can do is to change the initial command from "rsync" to "/usr/bin/rsync" (if that is where the real command is installed in your setup) in order to try to avoid any script & shell

Re: Rsync Daemon Remote Pull

2020-06-26 Thread Wayne Davison via rsync
On Thu, Jun 25, 2020 at 3:02 PM Chandrasekar Natarajan wrote: > Unexpected remote arg: user@x.x.x.x:port/module > This means that your non-option args starts with a local arg, contains a remote arg somewhere in the middle, and ends with either a local or remote arg. None of those are valid

Re: rsync with mode --delete

2020-06-26 Thread Wayne Davison via rsync
On Fri, Jun 26, 2020 at 10:24 AM Budi Janto wrote: > path = /mnt/DATA > Any idea or suggestion to prevent client's data loss? > There are several options: 1. Set the "pre-xfer exec = /script/name" in your daemon module and make the script check if a /mnt/DATA/known-to-exist-subdir is

[rsync-announce] Rsync 3.2.1 released

2020-06-22 Thread Wayne Davison via rsync-announce
I have released rsync 3.2.1. This is mainly a few fixes for some release issues and portability problems. There's also a couple new features, just for good measure. To see a summary of all the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS#3.2.1 You can download

Rsync 3.2.1 released

2020-06-22 Thread Wayne Davison via rsync
I have released rsync 3.2.1. This is mainly a few fixes for some release issues and portability problems. There's also a couple new features, just for good measure. To see a summary of all the recent changes, visit this link: https://rsync.samba.org/ftp/rsync/NEWS#3.2.1 You can download

[rsync-announce] Rsync 3.2.1pre1 released

2020-06-21 Thread Wayne Davison via rsync-announce
I have made rsync 3.2.1pre1 available for testing. This is mainly a few fixes for some release issues and portability problems. There's also a new feature, just for good measure. If no blocking issues are found, this will be released as 3.2.1 soon. To see a summary of all the changes since

Rsync 3.2.1pre1 released

2020-06-21 Thread Wayne Davison via rsync
I have made rsync 3.2.1pre1 available for testing. This is mainly a few fixes for some release issues and portability problems. There's also a new feature, just for good measure. If no blocking issues are found, this will be released as 3.2.1 soon. To see a summary of all the changes since

[rsync-announce] Rsync 3.2.0 released

2020-06-19 Thread Wayne Davison via rsync-announce
I have released rsync 3.2.0. This is a feature release with a number of bug fixes. To see a summary of all the changes since 3.1.3, visit this link: http://rsync.samba.org/ftp/rsync/rsync-3.2.0-NEWS You can download the source tar file and its signature from here:

Rsync 3.2.0 released

2020-06-19 Thread Wayne Davison via rsync
I have released rsync 3.2.0. This is a feature release with a number of bug fixes. To see a summary of all the changes since 3.1.3, visit this link: http://rsync.samba.org/ftp/rsync/rsync-3.2.0-NEWS You can download the source tar file and its signature from here:

[rsync-announce] Rsync 3.2.0pre3 released

2020-06-17 Thread Wayne Davison via rsync-announce
I have made rsync 3.2.0pre3 available for testing. This is mainly some improvements in configuration and portability fixes. Let's see if this one will end up being the last "pre" version before 3.2.0. Please give it a try! Send feedback via email to the rsync mailing list. Bugs can be created

Rsync 3.2.0pre3 released

2020-06-17 Thread Wayne Davison via rsync
I have made rsync 3.2.0pre3 available for testing. This is mainly some improvements in configuration and portability fixes. Let's see if this one will end up being the last "pre" version before 3.2.0. Please give it a try! Send feedback via email to the rsync mailing list. Bugs can be created

[rsync-announce] Rsync 3.2.0pre2 released

2020-06-15 Thread Wayne Davison via rsync-announce
I have made rsync 3.2.0pre2 available for testing. I got some nice feedback on a couple items in the pre1 release, so I decided to roll up that with a few other changes and release pre2. I'm hopeful that this will end up being the version that gets released as 3.2.0, so please give it a try!

Rsync 3.2.0pre2 released

2020-06-15 Thread Wayne Davison via rsync
I have made rsync 3.2.0pre2 available for testing. I got some nice feedback on a couple items in the pre1 release, so I decided to roll up that with a few other changes and release pre2. I'm hopeful that this will end up being the version that gets released as 3.2.0, so please give it a try!

[rsync-announce] Rsync 3.2.0pre1 released

2020-06-13 Thread Wayne Davison via rsync-announce
I have made rsync 3.2.0pre1 available for testing. This release has a bunch of fixes & new features. Please test the code and send feedback via email to the rsync mailing list. Bugs can be created via bugzilla tickets, github issues, or discussed on the mailing list. To see a summary of the

Rsync 3.2.0pre1 released

2020-06-13 Thread Wayne Davison via rsync
I have made rsync 3.2.0pre1 available for testing. This release has a bunch of fixes & new features. Please test the code and send feedback via email to the rsync mailing list. Bugs can be created via bugzilla tickets, github issues, or discussed on the mailing list. To see a summary of the

Re: bug: xattr filter rule treated as file filter rule on the remote side

2020-06-13 Thread Wayne Davison via rsync
On Wed, May 16, 2018 at 10:03 AM Andras Nagy wrote: > Summary: an xattr filter rule (e.g. --filter='-x! user.*’, which is > suggested by the documentation) is treated as a file filter rule on the > remote side. > This got fixed in git a long time ago, but I (sadly) haven't yet made a new release

Re: Rsync 3.1.3 segfault

2020-06-13 Thread Wayne Davison via rsync
On Mon, May 28, 2018 at 7:22 AM Marcin Krol wrote: > The code responsible for segfault is new popt_unalias function added > in 3.1.3. To be exact this line causes segfault: > poptAddAlias(con, unalias, 0); > I have never seen this crash occur, but it dawned on me that the reason is most likely

Re: Regarding an "earlier" variant of `pre-xfer exec` [feature request and proposed patch]

2020-06-11 Thread Wayne Davison via rsync
On Fri, Nov 8, 2019 at 8:00 AM Ciprian Dorin Craciun via rsync < rsync@lists.samba.org> wrote: > Therefore I've tried to patch `rsync` myself, mainly by copy-pasting the > code related to `pre-xfer exec` option: > >

Re: Delta-compression and --write-devices

2020-06-10 Thread Wayne Davison via rsync
On Wed, Jun 10, 2020 at 11:05 AM Laurens Blankers wrote: > Based on the log output and the source code I suspect that the problem > occurs because the delta-compression determines the size of the > destination to be 0. > Indeed, that looks to be exactly what is wrong. I adapted the code in the

Re: Preserving destination group and owner

2020-06-04 Thread Wayne Davison via rsync
On Thu, Jun 4, 2020 at 3:07 AM Alberto Cabello Sánchez wrote: > I'm trying to get an rsync updating some files without changing their > owner, groups or permissions. I've read man pages etc. stating I need to > use the "--no-o", "--no-g", "--no-p" flags > You'll need to also specify --inplace in

Re: Enabling easier contributions to rsync

2020-05-25 Thread Wayne Davison via rsync
On Mon, May 25, 2020 at 7:09 PM Karl O. Pinc via rsync < rsync@lists.samba.org> wrote: > FWIW, I find sending an email with an attachment a lot easier than having > to login to github, clone, push, and open a pull request. > Patches are still fine by me, so no mandatory pull requests here.

Re: Enabling easier contributions to rsync

2020-05-25 Thread Wayne Davison via rsync
I've decided to give hosting it on github a try, especially since there's been a lot of nice contributions lately. Hopefully this will make it easier for both the people sending patches as well as for me to snag the changes. I'll continue to push changes to the samba git as well. Here's the new

Re: [PATCH] Optimized assembler version of md5_process() for x86-64

2020-05-23 Thread Wayne Davison via rsync
On Sat, May 23, 2020 at 4:37 AM Sebastian Andrzej Siewior < rs...@ml.breakpoint.cc> wrote: > Wouldn't it be better to add support for a crypto library (like openssl) > which would provide optimized algorithms for more than just one platform > without the need to maintain it separately? > Adding

Re: checksum feature request

2020-05-23 Thread Wayne Davison via rsync
On Tue, Oct 1, 2019 at 8:02 AM Bill Wichser via rsync wrote: > Attached is the patch we applied [to add xxhash checksums] Thanks, Bill! I finally got around to finishing up some checksum improvements and have added support for xxhash in the master branch. The latest version in git now picks

Re: [PATCH] Optimized assembler version of md5_process() for x86-64

2020-05-23 Thread Wayne Davison via rsync
On Fri, May 22, 2020 at 11:08 AM Jorrit Jongma via rsync < rsync@lists.samba.org> wrote: > This patch introduces an optimized assembler version of md5_process(), the > inner loop of MD5 checksumming. It affects the performance of all MD5 > operations in rsync - including block matching and

Re: [PATCHv2] SSE2/SSSE3 optimized version of get_checksum1() for x86-64

2020-05-21 Thread Wayne Davison via rsync
On Tue, May 19, 2020 at 7:29 AM Jorrit Jongma via rsync < rsync@lists.samba.org> wrote: > I've read up some more on the subject, and it seems the proper way to do > this with GCC is g++ and target attributes. I've refactored the patch that > way, and it indeed uses SSSE3 automatically on

Re: [draft PATCH] whitelist support for refuse options

2020-05-17 Thread Wayne Davison via rsync
On Sun, Feb 9, 2020 at 2:06 PM Nick Cleaton via rsync wrote: > This adds support for whitelisting the acceptable options in the "refuse > options" setting in rsyncd.conf. It introduces "!" as a special option > string that refuses most options and interprets any following strings as > patterns

Re: How to display IP of mirror site and exclude it

2020-04-22 Thread Wayne Davison via rsync
On Wed, Apr 8, 2020 at 8:15 AM Gerard E. Seibert wrote: > Since this does not happen on all of the mirror sites, I would like a way > to get a list or have rsync display the IP of the site it received an error > message from and a way to block the use of that IP in the future. Is that > possible?

Re: [PATCH] Replace mkproto.pl with mkproto.awk

2020-04-07 Thread Wayne Davison via rsync
Thanks for the patch! I've gone ahead and included it in the latest git since it should make a standard build a little simpler. I do note that for any patched builds where the yodl (.yo) doc files got changed that there is still a perl dependency when running the tweak_manpage script on the

Re: Allow "--in-place" as an alternative option name for "--inplace"

2020-04-05 Thread Wayne Davison via rsync
> On Jun 26, 2019, at 2:53 PM, Jan-Benedict Glaw via rsync < rsync@lists.samba.org> wrote: > > As I commonly spell --inplace as --in-place, I'd like to suggest this simple patch: On Wed, Jun 26, 2019 at 7:29 PM @lbutlr via rsync wrote: > If we’re going to do that add --remove-source and

Re: [PATCH] Bug fix for file comparison

2019-03-16 Thread Wayne Davison via rsync
On Thu, Mar 7, 2019 at 12:27 AM Florian Zumbiehl via rsync < rsync@lists.samba.org> wrote: > in the file comparison code: The > current code skips the unchanged_file() check when that check succeeded for > an earlier candidate, which could lead to accepting a file with a different > checksum as

Re: zlib issues

2019-03-16 Thread Wayne Davison via rsync
On Wed, Mar 13, 2019 at 6:02 AM Christoph Gentsch via rsync < rsync@lists.samba.org> wrote: > I just had a look at the rysnc code (master branch) and realized, that > there is a copy of the zlib included. So I checked if the CVEs from 2016 > are patched in this, and NOPE! they arent! > Thanks

Re: preallocate working incorrectly in 3.1.3

2019-01-15 Thread Wayne Davison via rsync
On Mon, Jan 14, 2019 at 6:11 PM TR Reardon via rsync wrote: > I believe that the changes to support --preallocate and --sparse together > have broken --preallocate by itself (commit > f3873b3d88b61167b106e7b9227a20147f8f6197) > Indeed, those "opts" values were reversed, and thus fallocate

Re: rsync sends -C and -x options silently

2018-05-16 Thread Wayne Davison via rsync
On Wed, May 16, 2018 at 10:04 AM Anand Buddhdev via rsync < rsync@lists.samba.org> wrote: > This newer rsync version appears to be sending -C and -x options to the > server, even though they are not set on the client side. > It's not. What it is doing is sending information in the -eSTRING

Re: Unfortunate results from fake-super

2018-02-04 Thread Wayne Davison via rsync
On Sat, Feb 3, 2018 at 5:20 AM, Dave Gordon via rsync wrote: > [...fake-super symlink saved as a file...] This results in the copy being world-writable. > Indeed. The file initially gets created as a mode-600 file, but the code later tweaks the permissions to match the

[rsync-announce] Rsync 3.1.3 released

2018-01-28 Thread Wayne Davison via rsync-announce
Rsync 3.1.3 is now available for downloading. This is a security, feature, and bug-fix release. To see a full summary of the changes since 3.1.2, visit this link: http://rsync.samba.org/ftp/rsync/src/rsync-3.1.3-NEWS You can download the source tar file and its signature from here:

Rsync 3.1.3 released

2018-01-28 Thread Wayne Davison via rsync
Rsync 3.1.3 is now available for downloading. This is a security, feature, and bug-fix release. To see a full summary of the changes since 3.1.2, visit this link: http://rsync.samba.org/ftp/rsync/src/rsync-3.1.3-NEWS You can download the source tar file and its signature from here:

Re: Rsync 3.1.3pre1 released

2018-01-15 Thread Wayne Davison via rsync
On Mon, Jan 15, 2018 at 6:20 AM, Randall S. Becker wrote: > Incompatibility introduced at 3.1.3pre1. These are not present at master, > which compiles cleanly. > The master branch and 3.1.3pre1 were pretty much the same until just a moment ago (except that the tar files

Rsync 3.1.3pre1 released

2018-01-14 Thread Wayne Davison via rsync
I have made rsync 3.1.3pre1 available for testing. This release has a couple security fixes, a few new features, and a smattering of bug fixes. Please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. To see a summary of the changes

Re: read dir list with write only option

2017-10-08 Thread Wayne Davison via rsync
On Wed, Sep 6, 2017 at 1:00 AM, Pavel Kasparek via rsync < rsync@lists.samba.org> wrote: > when the "write only = yes" option is used on rsync server, [... would a] > hacked client [...] be able to get the list of remote dir [?] It wouldn't work. The listing action is a special kind of read

Re: --no-omit-dir-times does not override --backup

2017-10-08 Thread Wayne Davison via rsync
On Sat, Sep 16, 2017 at 10:13 AM, Anders Gronberg via rsync < rsync@lists.samba.org> wrote: > As I understand the documentation "--backup" without specifying > "--backup-dir" implicitly sets "--omit-dir-times". > It is then possible to negate the implied option by specifying it prefixed > with

Re: rsync buffer overflow detected

2017-04-29 Thread Wayne Davison via rsync
On Fri, Apr 14, 2017 at 10:22 AM, Boris Savelev via rsync < rsync@lists.samba.org> wrote: > #8 0x55585ef6 in read_int (f=f@entry=1606) at io.c:1711 > #9 0x555876ed in setup_protocol (f_out=1605, f_in=1606) at > compat.c:158 > Since rsync is just trying to setup the protocol,

Re: How do you exclude a directory that is a symlink?

2017-03-05 Thread Wayne Davison
On Fri, Mar 3, 2017 at 7:48 AM, Ken Chase wrote: > I think both situations could benefit from a --resolve-cmd-line-links > switch to resolve COMMAND LINE-SUPPLIED symlinks. > You can specify symlinks in a --relative path with a trailing slash-dot (and use /./ infix

Re: How do you exclude a directory that is a symlink?

2017-03-05 Thread Wayne Davison
On Fri, Mar 3, 2017 at 4:41 AM, Steve Dondley wrote: > However, if I add a --copy-links option to the command, it appears to > override my "exclude" directive and the contents of the symlinked directory > gets downloaded anyway. > The use of --copy-links doesn't do that, so

Re: why "DEFAULT" ?

2017-02-20 Thread Wayne Davison
On Wed, Jan 25, 2017 at 7:22 AM, Дугин Сергей wrote: > %G the gid of the file (decimal) or "DEFAULT" > > Why "DEFAULT"? > The DEFAULT usually indicates that rsync isn't preserving the gid value at all (so it doesn't have any group info for the file) but it can also mean that the

Re: [PATCH v2 1/2] xattrs: Skip security.evm extended attribute

2017-01-22 Thread Wayne Davison
On Mon, Jan 9, 2017 at 2:31 PM, Stefan Berger wrote: > GNU tar for example requires to use --xattrs-include=pattern to indicate > which extended attributes to put into the archive. It also support > --xattrs-exclude=pattern. Maybe something along those lines could

Re: Links repeatedly being copied???

2016-10-29 Thread Wayne Davison
On Sun, Oct 16, 2016 at 1:17 PM, B. S. wrote: > I have for the longest time been seeing '.L..t..'s in my rsync log, > despite no changes to such in quite some time, and in trying to track it > down, been baffled. > This means that rsync is trying to set the timestamp on

Re: -e escape rule

2016-10-29 Thread Wayne Davison
On Sat, Oct 29, 2016 at 5:36 AM, Samuel Williams < space.ship.travel...@gmail.com> wrote: > The command > > ssh -l backup -i /etc/synco/id_rsa -o ConnectTimeout\=60 -o BatchMode\=yes > > Is a correct and valid shell command. > It is, but there is no shell involved, and assuming that a shell is

Re: rsync send "non-rsync" options to the server side (--remote-option) and (--protect-args)

2016-10-28 Thread Wayne Davison
If you want to pass non-rsync args (etc) you should be using --rsync-path. The -M option is only for sending rsync-related options. ..wayne.. On Fri, Oct 28, 2016 at 7:32 AM, John Lane wrote: > > Hello, I asked the below back at the beginning of August but have > received no

Re: -e escape rule

2016-10-28 Thread Wayne Davison
On Fri, Oct 28, 2016 at 5:39 AM, Samuel Williams < space.ship.travel...@gmail.com> wrote: > Rsync passed the backslashes through without dealing with them. > Yeah, it only does space-splitting and that's all it will ever do. It still looks to me like there is a bug in the original escaping,

Re: rsync unexpectedly removing ALL files

2016-06-12 Thread Wayne Davison
On Mon, Jun 6, 2016 at 8:52 AM, Koehn, Troy N. wrote: > One of the directories in the database actually looked like this: > > > > /home/usr/directory/./ > In the manpage under the "--relative" option (which is implied by --files-from) there is this information: It is also

Re: Deletion of destination files

2016-06-05 Thread Wayne Davison
On Sun, Jun 5, 2016 at 6:39 AM, Steven Levine wrote: > > $ rsync --dry-run -vrt --delete --modify-window=1 file1 file2 file3 ... > >/mnt/pendrive/rodolfo > > >not happen. In rsync `man' page I can't find a solution. > >From the man page's description of --delete: This

Re: Yet another filter question

2016-05-04 Thread Wayne Davison
On Tue, May 3, 2016 at 1:07 PM, Christoph Biedl wrote: > + *.git/.git/* > - *.git/ > >From the man page near the start of the "INCLUDE/EXCLUDE PATTERN RULES" section: *Note that, when using the --recursive (-r) option (which is implied by > -a), every subcomponent of every

Re: [PATCH] Consider nanoseconds when quick-checking for unchanged files

2016-01-20 Thread Wayne Davison
On Thu, Dec 25, 2014 at 2:48 AM, Ingo Brückl wrote: > On systems using nanoseconds differences should be taken into > consideration. > The problem is that if you transfer from a filesystem that has nanoseconds to one that does not support it, rsync would consider most of

Re: Rsync 3.1.1 released

2015-12-21 Thread Wayne Davison
Rsync 3.1.2 is now available for downloading. This is a bug-fix release. To see a full summary of the changes since 3.1.1, visit this link: http://rsync.samba.org/ftp/rsync/src/rsync-3.1.2-NEWS You can download the source tar file and its signature from here:

Rsync 3.1.2 released

2015-12-21 Thread Wayne Davison
Rsync 3.1.2 is now available for downloading. This is a bug-fix release. To see a full summary of the changes since 3.1.1, visit this link: http://rsync.samba.org/ftp/rsync/src/rsync-3.1.2-NEWS You can download the source tar file and its signature from here:

Re: Doubt on usage of rsync for chown of existing folders

2015-09-13 Thread Wayne Davison
On Thu, Sep 10, 2015 at 6:58 PM, Celso de Sousa Junior < celso_de_sousa_jun...@yahoo.com.br> wrote: > I would like to have changes (chown) in the destination. > I suggest using the --super option so that you ensure that the receiving side attempts to chown the files, and you'll get warned if it

Re: Error with paths with ()'s

2015-08-17 Thread Wayne Davison
On Sun, Aug 16, 2015 at 11:13 PM, @lbutlr krem...@kreme.com wrote: find . -type f -atime -1 -exec rsync -aP {} 10.0.0.11:/Volumes/Drive5/{} \; The use of {} on the receiving (remote) side is superfluous -- just specifying a destination dir (your .../Drive5/ path) is enough for rsync to use

Rsync 3.1.2pre1 released

2015-08-08 Thread Wayne Davison
I have just made rsync 3.1.2pre1 available for testing. This is a bug-fix release that fixes a few important issues and makes a some minor improvements. Please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. To see a summary of the

Re: unnecessary /proc requirement in 3.1.1

2015-08-02 Thread Wayne Davison
On Sat, Aug 1, 2015 at 4:21 AM, Fyodorov Bga Alexander bga.em...@gmail.com wrote: Whole /proc is serious security risk for me. Why? You'll have to ask your system libraries that question, since it is them that are querying /proc. Your extra chrooting is forcing even the root-level actions

Re: C coding tips please / Localisation

2015-07-12 Thread Wayne Davison
On Fri, Jul 10, 2015 at 5:57 PM Michael cuscotravelservi...@gmail.com wrote: However, given the warning messages I saw, maybe this is not the correct (elegant and most efficient) way for the secondary files to reference libintl.h. The best place to add that include and the gettext define

Re: A question about CVE-2014-8242

2015-05-13 Thread Wayne Davison
On Mon, May 11, 2015 at 10:38 PM, yhu2 yadi...@windriver.com wrote: Thanks your explanation, how about MD4 (rsync protocal 30)? any comment would be appreciated!! The MD4 checksum in older protocols doesn't have the issue. ..wayne.. -- Please use reply-all for most replies to avoid

Re: A question about CVE-2014-8242

2015-05-11 Thread Wayne Davison
On Mon, May 11, 2015 at 12:50 AM, yhu2 yadi...@windriver.com wrote: whether or not CVE-2014-8242 affects rsync? any commnet would be appreciated!! Yes. It would be extremely hard for someone to trigger that via indirect means (such as inserting DB data and managing to match a checksum

Re: Using external filter on the server

2015-05-04 Thread Wayne Davison
On Wed, Apr 29, 2015 at 2:52 AM, Mark mark0...@gmail.com wrote: I have added the filter to the rsyncd.conf on the source server, which receives the native client connection over a network. filter='-!| newer-filter mm/dd/yy' That was a suggested syntax for a feature that nobody

Re: Is it possiable to suppress the site-specified messages?

2015-04-19 Thread Wayne Davison
On Fri, Apr 17, 2015 at 8:51 PM, Hongyi Zhao hongyi.z...@gmail.com wrote: When connect to a remote rsync server, often it will give some site-specified messages [...] If I want to suppress the messages [...] You're talking about the motd, which has this option mentioned in the manpage:

Re: Finding specific files/directories from a remote rsync server.

2015-04-12 Thread Wayne Davison
On Fri, Apr 10, 2015 at 4:11 PM, Hongyi Zhao hongyi.z...@gmail.com wrote: Say, if I want to find all of the `foo/file' on this rsync server You'd use filter (include/exclude) rules. See in the man page about its notes on how rsync requires you to include all directories in order to traverse

Re: rsync --link-dest won't link even if existing file is out of date

2015-04-12 Thread Wayne Davison
On Sun, Apr 5, 2015 at 10:51 PM, Ken Chase rsync-list-m...@sizone.org wrote: Feature request: allow --link-dest dir to be linked to even if file exists in target. From the release notes for 3.1.0: - Improved the use of alt-dest options into an existing hierarchy of files: If a match

Re: rsync splits filenames, creates special characters where none are, weird permissions

2015-01-07 Thread Wayne Davison
On Wed, Jan 7, 2015 at 7:16 AM, Lenz Weber m...@lenzw.de wrote: [...] rsyncbackup@server:/var/backups/mail/. [...] Does that login force a particular rsync command via ssh's authorized_keys file? It looks like the data stream is being garbled, and one way that could happen is if the

Re: Modification time error

2014-12-31 Thread Wayne Davison
On Wed, Dec 31, 2014 at 2:34 AM, Ingo Brückl i...@wupperonline.de wrote: /tmp was actually on a tmpfs and no idea why this happens Thanks for pointing that out. I couldn't reproduce the issue until I ran the tests on a tmpfs mount, and discovered that rsync is optimizing away a utimensat()

Re: Behaviour of --append with modified files

2014-12-31 Thread Wayne Davison
On Mon, Dec 15, 2014 at 9:06 PM, Mark Stead mark.st...@unico.com.au wrote: Is there any option that I've overlooked whereby I can force rsync to synchronise modified files (in addition to handling appended files). No, rsync expects you to handle just appended files in --append mode. You

Re: Bug-report:rsync may hung if time jumps backwards

2014-11-27 Thread Wayne Davison
On Sun, Nov 16, 2014 at 10:44 PM, yhu2 yadi...@windriver.com wrote: + usleep(t*1000); Is it a correct fix? any comments would be appreciated!!! The hang was not because time went backwards, but because it moved forward by over 2 years (which overflows a variable, making the value negative).

  1   2   3   4   5   6   7   8   9   10   >