similar to: [Bug 1812] fuzzy not working in 2.6.3-pre{1,2}

https://bugzilla.samba.org/show_bug.cgi?id=1812 Summary: fuzzy not working in 2.6.3-pre{1,2} Product: rsync Version: 2.6.3 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: egmont@uhulinux.hu

https://bugzilla.samba.org/show_bug.cgi?id=3392 Summary: fuzzy misbehaving if source is a file Product: rsync Version: 2.6.6 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: egmont@uhulinux.hu

On 5 Jan 2005, Rusty Russell <rusty@rustcorp.com.au> wrote: > On Tue, 2005-01-04 at 18:24 +0100, Robert Lemmen wrote: > > hi rusty, > > > > i read on some webpage about rsync and debian that you wrote a patch to > > rsync that let's it uses heuristics when deciding which local file to > > use. could you tell me whether this is planned to be included in

http://bugzilla.mindrot.org/show_bug.cgi?id=789 Summary: pam_setcred() not being called as root Product: Portable OpenSSH Version: 3.7.1p2 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: PAM support AssignedTo: openssh-bugs at mindrot.org ReportedBy:

http://bugzilla.mindrot.org/show_bug.cgi?id=789 Summary: pam_setcred() not being called as root Product: Portable OpenSSH Version: 3.7.1p2 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: PAM support AssignedTo: openssh-bugs at mindrot.org ReportedBy:

https://bugzilla.samba.org/show_bug.cgi?id=1488 Summary: rusty-fuzzy.diff lacks a new file Product: rsync Version: 2.6.2 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: egmont@uhulinux.hu QAContact:

http://bugzilla.mindrot.org/show_bug.cgi?id=871 Summary: request for idn (intl domain names) support Product: Portable OpenSSH Version: 3.8.1p1 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: Miscellaneous AssignedTo: openssh-bugs at mindrot.org

https://bugzilla.samba.org/show_bug.cgi?id=1489 Summary: Corrupt transfer with the fuzzy option Product: rsync Version: 2.6.2 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: egmont@uhulinux.hu

Wayne, It's taken a little while for me to get more familiar with the code, but I think I've reached a good breakpoint in improving batch-mode. Let me highlight some of the changes in the attached patch: * --write-batch and --read-batch arguments are no longer passed from client to server. This fixes the current problem that causes the server threads to die when the client

hi. return value of close() (receiver.c) is ignored. when running out of quota on NFS (for example), this can happen (without the patch): output file(s) is/are truncated to 0 bytes and rsync reports success. with the fix, this happens: close "/home/luser/.test.mp3.PwaG50": Disc quota exceeded rsync error: error in file IO (code 11) at receiver.c(464) ... ...and additionally, test.mp3

The generator can skip a directory's contents altogether due to --ignore-non-existing, a daemon exclude, or a mkdir failure. On a --dry-run, the generator can also note the missingness of a directory while still scanning its contents. These two scenarios were conflated using a single set of missing_below/missing_dir variables in combination with transient increments in dry_run; this caused

Hi, I just noticed that the value of the '--compare-dest' argument is simply prepended to the DEST argument, even if that has path compnents. For example with this command: rsync -a --compare-dest=$comparedest \ remote::something/1/ \ /local/path/to/1/ if the remote 'something' module has a file called '1/2/3/4/file' (which is going to be mirrored to

Included below is a shar archive containing two patches that together: 1) make backup files get their setuid and setgid bits stripped by default 2) add a "-s" option that allows backup files to continue to have these privileges This means that if you update a collection of binaries with rsync, and one or more of them has a local-root security problem, the backup file(s) created when

Hi, I use rsync in the following way to update some remote files over a low bandwidth line: rsync -v -r -z -t -p <local dir> <user>@<host>:<dir on host> After updating from rsync 2.5.2 to 2.5.4 I noticed that modified files are always copied completely. The problem seems to be related to the new (in 2.5.3) option -no-whole-file. The global variable whole_file is

https://bugzilla.samba.org/show_bug.cgi?id=10581 Summary: --fuzzy-delay and --fuzzy-limit for fuzzy match tuning Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: samba at

Hi, I needed to filter content of files (encrypt), before they are sent over the network to backup server. The easiest way to do this was modifying Kyle Jones's "--dest-filter" patch. Somebody was asking there this feature in the past, so I'm sending this patch to list. Implementation details: -filtering disables rsync alogrithm -source filter makes temporary files in /tmp

https://bugzilla.samba.org/show_bug.cgi?id=12489 Bug ID: 12489 Summary: --fuzzy --fuzzy does not work with daemon Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

I've identified a situation where the combination of --fuzzy --fuzzy (yes: two of them) and --link-dest is not behaving as I'd expect. I'm first wondering if my expectation is wrong. Assuming that it is not, then I'm wondering how best to figure out the problem. The double use of --fuzzy is based upon https://bugzilla.samba.org/ show_bug.cgi?id=4056 which should be present on

https://bugzilla.samba.org/show_bug.cgi?id=12498 Bug ID: 12498 Summary: --fuzzy --fuzzy hugely impacts performance even if its' not needed Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

Dear samba-users We are experiencing some rather long logon times using SAMBA 3.5.6 on Debian Squeeze + Windows 7 and while trying to find out why we raised the loglevel to 5 resulting in a rather large logfile. But this did give us a hint as to why we experience so long logon times. It seems that samba is going through the whole user-database with all usernames and machine-accounts. Eventually