similar to: read error produces null-byte-filled destination file

All callers of robust_rename() call copy_file() if EXDEV is received. This patch moves the copy_file() call into robust_rename(). Patch Summary: -12 +1 backup.c -15 +2 rsync.c -9 +33 util.c -------------- next part -------------- patchwork diff util.c --- util.c 2004-02-17 09:58:44.000000000 -0500 +++ util.c 2004-02-17 10:21:22.000000000 -0500 @@ -355,16 +355,40 @@

There is a small race condition in rsync 2.5.6. When the transfer is finished, and the file is moved into place, there is a short time period where the new file is in place with the wrong permissions. When using rsync on a busy email server to replace the exim config file with a new file, exim will produce several complaints in that short period. This small patch fixes the problem, by making

The attached patch provides an additional check for the checksumming mode to ensure that a file that is actually written out to disk can be read back and has the same MD4 sum as the file on at the originating location. Regards, Nick. -------------- next part -------------- *** rsync-2.6.6pre1/receiver.c 2005-04-14 02:42:13.000000000 +0100 --- rsync-new/receiver.c 2005-07-26

I am running RedHat 6.2 on many of my servers and am receiving the following errors when compiling Rsync 2.5.2: [root@wrapguy rsync-2.5.2]# make gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c rsync.c -o rsync.o In file included from rsync.c:23: rsync.h:339: warning: no semicolon at end of struct or union rsync.h:339: parse error before `inode' rsync.h:341: parse error before `dev'

I came up with a patch to fix the problem of IO Errors caused by excluded files as did Eugene V. Chupriyanov below. Is there a chance that this change will show up in a future version of rsync? Is there a reason that we should not ignore IO errors when copy_links is off? Just want to make sure that I'm not missing something here that may corrupt my syncs.... Here's the version that

I have attached a patch that supports a new "--direct-write" option. The result of using this option is to write directly to the destination files, instead of a temporary file first. The reason this patch is needed is for rsyncing to a device where the device is full or nearly full. Say that I am writing to a device that has 1 Meg free, and a 2 meg file on that device is out of date.

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

This is a patch to fix one annoyance of having rsync processes race: I usually keep our servers synced with the following script, run by cron. #!/bin/sh lockfile -r 2 -l 1000 /tmp/synchome.lock || exit 1 rsync -e ssh -avHP --delete zorro01:/home/\* /home >/dev/null rm -f /tmp/synchome.lock -- Sometimes my users (including myself) are in a hurry and syncronise files and directories in their

I've been having problems trying to sync two small partitions (128MB) that may be near to full. If rsync gets a write error (such as is caused when you fill up a partition) during a sync without the use of "-T", it will stop with this error: rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream

I've recently encountered this issue which was discussed here about a year ago. I'm not sure if anyone has a fix for this, but I thought I would post my workaround here. Since the topic is old, I'm summarising the problem .. basically it involves rsync creating large numbers of files with a leading ".." when syncing to an apple network share via afp. The essence of the

Hi, As the man page says, the --partial flag is to "keep partially transferred files". I'm assuming if I don't have partial flag any partially transferred files should be deleted. However this is not what I'm seeing. Example: (Using a big file so that rsync times a while to run. This gives me time to hit CTRL-C for the SIGINT). > mkdir example > dd if=/dev/zero

Trying to compile rsync 2.5.2 after "./configure --prefix=/usr" I get the following make errors: gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c rsync.c -o rsync.o In file included from rsync.c:23: rsync.h:339: warning: no semicolon at end of struct or union rsync.h:339: parse error before `inode' rsync.h:341: parse error before `dev' rsync.h:341: warning: type

[I sent this the other day, but it never got approved for the list] I've been having problems trying to sync two small partitions (128MB) that are usually near being full. The rsync would fail with this cryptic error: rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) It ends up

This patch adds the --link-by-hash=DIR option, which hard links received files in a link farm arranged by MD4 file hash. The result is that the system will only store one copy of the unique contents of each file, regardless of the file's name. (rev 2) * This revision is actually against CVS HEAD (I didn't realize I was working from a stale rsync'd CVS). * Apply permissions after

https://bugzilla.samba.org/show_bug.cgi?id=8847 Summary: detect-renamed.diff update to ensure existence of directory for partial-dir Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1322568055 0 # Node ID 6da8c30fb198adc15136a867a8303b7de3804bcf # Parent fa9deee858b84d4c4fbb5f9523fa5adb7aac3a35 docs: XenBus page has been transfered to new wiki Signed-off-by: Ian Campbell <Ian.Campbell@citrix.com> diff -r fa9deee858b8 -r 6da8c30fb198 docs/misc/xenstore.txt --- a/docs/misc/xenstore.txt Tue

Hi There, This post is brought about due to the following two: http://www.mail-archive.com/rsync@lists.samba.org/msg10702.html http://www.mail-archive.com/rsync@lists.samba.org/msg10709.html I have a situation where I need to upload large files over an unstable link (resuming is a requirement) and only when they are complete can they be renamed and hence replace the original file. The

What patch files are necessary to build rsync-3.0.9 for OS X 10.6.8 (Darwin 10.8.0)? Mr. Bombich maintains an excellent page about this, but it's a bit out of date, methinks, and his instructions point to patch files that return some interesting errors. My rsync-3.0.9 is working just fine, btw, with the fileflags and crtimes and hfs-compression patches applied; I just wondered if the others

https://bugzilla.samba.org/show_bug.cgi?id=5147 Summary: Read-only files that have changed xattrs fail to allow xattr changes Product: rsync Version: 2.6.9 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi, Is there a way to change the permission for a specific path in XenStore? And can you do that from with in a C program? Thanks Julian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel