similar to: DO NOT REPLY [Bug 5091] New: Incremental-recursive, list-only "rsync --delete" tries to clean out working dir

Displaying 20 results from an estimated 7000 matches similar to: "DO NOT REPLY [Bug 5091] New: Incremental-recursive, list-only "rsync --delete" tries to clean out working dir"

2005 Jan 05
1
rsync filename heuristics
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
2002 Jan 07
0
rsync-2.5.1 / updated syscall.c "const" patch
Operating System: OpenVMS ALPHA V7.3 Compiler: Compaq C T6.5 Compiler switches: /WARN=ENABLE=(LEVEL4, QUESTCODE) syscall.c is missing the "const" qualifiers for several of it's functions. This patch should supercede the previous patch I submitted. This was discovered while working on resovling the conflicts between signed and unsigned values. -John wb8tyw@qsl.network Personal
2008 Mar 19
0
[PATCH] Unsnarl missing_below/dry_run logic.
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
2004 Jun 17
1
[PATCH] make write_batch local
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
2007 Aug 03
4
DO NOT REPLY [Bug 4855] New: skipped local filters cause segfault while deleting (-rFR --delete)
https://bugzilla.samba.org/show_bug.cgi?id=4855 Summary: skipped local filters cause segfault while deleting (- rFR --delete) Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org
2008 Jan 13
2
DO NOT REPLY [Bug 5190] New: rsyncd can't unlink dir structure when only the group has write permission
https://bugzilla.samba.org/show_bug.cgi?id=5190 Summary: rsyncd can't unlink dir structure when only the group has write permission Product: rsync Version: 2.6.9 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo:
2008 Dec 05
0
rsync patch to allow content from one device file to be synced to another device file
I noticed that this topic appeared from time to time on the mailing list and that one patch exists (copy-devices.diff) from a previous thread which allowed rsync to operate with a source device file. The patch below, when combined with the 'copy-devices' patch, allows rsync to be operate between two device files. In our environment this is being used, along with LVM snapshots, to
2008 Feb 16
1
DO NOT REPLY [Bug 5266] New: Duplicate "not creating new directory" output w/ incremental recursion
https://bugzilla.samba.org/show_bug.cgi?id=5266 Summary: Duplicate "not creating new directory" output w/ incremental recursion Product: rsync Version: 3.0.0 Platform: Other OS/Version: Linux Status: NEW Severity: minor Priority: P3 Component: core AssignedTo:
2009 Sep 13
1
DO NOT REPLY [Bug 6719] New: I/O error protection is broken w/ protocol 30 and incremental recursion
https://bugzilla.samba.org/show_bug.cgi?id=6719 Summary: I/O error protection is broken w/ protocol 30 and incremental recursion Product: rsync Version: 3.0.6 Platform: All OS/Version: All Status: NEW Severity: critical Priority: P3 Component: core AssignedTo: wayned at
2008 Mar 20
2
DO NOT REPLY [Bug 5343] New: rsync does nothing after first time
https://bugzilla.samba.org/show_bug.cgi?id=5343 Summary: rsync does nothing after first time Product: rsync Version: 3.0.0 Platform: IA64 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: rolmol@broadpark.no
2003 Sep 05
1
new option suggestion '--backup-only'
Hi, How about adding now option '--backup-only' that means making backups only and don't change any destination files? (I posted similar patch a month ago, but the patch was made for nightly snapshot of 20020808, which was tooo old! Laugh at me...) I want to use rsync with LVM snapshot to make incremental backups like below: 1) Make LVM snapshot of file system and mount it.
2004 Jan 17
1
--delete-sent-files (AKA --move-files)
Yes, it's time once again to return to the subject of moving files. With the recent changes to the communications code between the receiver and the generator, there is now a non-clogging channel that we can use to signal the sender when a file has been successfully transferred, which allows us delete the original for all transferred files. I have in the past waffled on whether this feature
2006 Jul 14
2
DO NOT REPLY [Bug 3935] New: replacing a full directory with symlink with --delete-after produces cryptic message
https://bugzilla.samba.org/show_bug.cgi?id=3935 Summary: replacing a full directory with symlink with --delete- after produces cryptic message Product: rsync Version: 2.6.6 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:
2005 Mar 21
4
Patch: Offline transfer mode
Hi All, Here's an rsync patch which adds an --offline flag, letting you transfer changed blocks via removable media, while still comparing checksums via the net. I expect this could be very popular for the growing number of people who want to do disk-based offsite backups, which is what I needed it for. It took me longer than I hoped, but still only several hours to work this out -- it
2002 Apr 03
3
metadata in dryrun mode
As I reported a while back rsync doesn't handle metadata (permissions and ownership) in dryrun mode. I offered to make a patch and that offer still stands. I didn't have the time for it until now and want to pick it up again. I had some ugly hack back then but I want to redo it in a clean way. I would like some input on my thoughts. IMHO, it would be ideally if the check for dry_run
2004 Apr 20
1
improved atime patch
I posted a patch a few days ago that adds copying of atime. At that time, it was just enabled with -t/--times. After some time, we have figured out that that choice might not have been the best. Here's a new version of the patch (relative to CVS) that adds -A/--copy-atime instead. It also includes a test case. Any feedback on this patch and/or the previous one that I posted?
2002 May 22
1
rsyncd listing of directories
I just took a look at the 2.5.5 codebase to see how easy it would be to write a little driver script that downloads a big directory tree from an rsync daemon the chunky way (get a list of a module's subdirectories and do the transfer by subdirectory). The reason for doing this is obvious when you have large directory trees, as is the case for many of us. Unfortunately the way list_only is
2004 Apr 10
0
patches for copying atimes
Hi. Here's a patch for copying the atimes of files when -t/--times is given. I bumped the protocol to 29 since it sends more data over the wire. It obviously does not send the atime if it's sending data to an older rsync version. It passes all the tests (including the added atime.test) for me on a: Linux Debian/3.0 gcc 2.95.4 (debian), glibc 2.2.5 system. Any questions/feedback? I
2009 Aug 13
3
DO NOT REPLY [Bug 6636] New: Deallocation of a pointer not malloced
https://bugzilla.samba.org/show_bug.cgi?id=6636 Summary: Deallocation of a pointer not malloced Product: rsync Version: 3.0.6 Platform: PPC OS/Version: Mac OS X Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: aaro at iki.fi
2005 Feb 25
1
smbclient's tar to /dev/null behaves unexpectedly
If I use smbclient to create a tar file at /dev/null, it skips most of the steps. This behavior If I type something like this: smbclient '\\puffin\c$' -U 'amanda%password' -E -d1 -Tca /dev/null '/Kathy/DATA/2120 WNmod/*' I receive the following message: Output is /dev/null, assuming dry_run source/client/clitar.c: if (tar_type=='c' && (dry_run ||