similar to: Problem found and fixed with --update

Displaying 20 results from an estimated 400 matches similar to: "Problem found and fixed with --update"

2004 Apr 27
1
[PATCH] Inplace option for rsync
Hi, I have written a 'smallish' patch to implement the --inplace option as discussed on this mailing list at various points in the past. It makes a small modification to the sender algorithm so that it won't ask the receiver to relocate blocks from earlier in the file when running with the --inplace option. I would appreciate any testing and feedback people can provide! I
2003 May 21
2
patch to avoid race condition in rsync 2.5.6
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
2001 Nov 13
2
direct write patch
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.
2002 Jul 24
0
couple of minor fixes to rsync 2.5.5
Dear friends! I really appriciate the great job you did on rsync package and hope for its further improvement and development. It works great in our pretty complex environment and helps us a lot in our daily duties. But we've run into couple of small inconveniences. First one: We use rsyncd to propagate a tree of html files among several web-servers. That files are generated on the fly and
2004 Feb 17
0
[patch] Add `--link-by-hash' option (rev 3).
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 3) * Don't link empty files. * Roll over to new file when filesystem maximum link count is reached. * If link fails for another reason, leave
2004 Feb 23
0
[patch] Add `--link-by-hash' option (rev 5).
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 5) * Fixed silly logic error. (rev 4) * Updated for committed robust_rename() patch, other changes in CVS. (rev 3) * Don't link empty
2004 Feb 23
0
[patch] Add `--link-by-hash' option (rev 4).
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 4) * Updated for committed robust_rename() patch, other changes in CVS. (rev 3) * Don't link empty files. * Roll over to new file when
2004 Apr 27
1
rsync-2.6.1 close() fixes
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
2002 Dec 05
1
Patch to ignore exluded files.
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
2004 Feb 16
1
[patch] Add `--link-by-hash' option (rev 2).
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
2009 Mar 11
0
Odd issue with locked directories and Mac OS X
Some of my users have reported problems with rsync puking on locked folders. The errors typically look like this: rsync -aNHAXx --fileflags --force-change --no-inc-recursive / /Volumes/ Backup > rsync: mkstemp "/Volumes/SCSI Backup/Users/Ken/Library/Caches/ > Metadata/Safari/Bookmarks/..DS_Store.N9xtNy" failed: Operation not > permitted (1) (51) > rsync: mkstemp
2004 Feb 17
1
[patch] Make robust_rename() handle EXDEV.
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 @@
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.
2002 Jun 07
0
problem related to filename length
hi, all. I had an problem with rsync-2.5.4/5 related to filename length. On Linux box (kernel-2.4.18 + ext3 fs), filename length limits to 255byte, but rsync can't handle fn > (255 -9) byte. So I had an instant hack to avoid this problem. Patch file attatched works fine in my case, but I'm not sure that it is correct or not. Any suggestions ? Please cc me, I'm not on this
2011 Feb 24
1
osx 10.6 strange rsync errors
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
2011 Apr 05
2
osx 10.6 strange rsync errors
Hi Rob / Wayne, Sorry for the slow reply Rob. I'm not sure of the requirements for patches, but I think it would be useful to create one for this case as there are reasonably number of people affected. I created a patch file against the current version (see below). Would it be possible to include this patch in the official list? Cheers Ira diff -Naur rsync-3.0.8_orig/receiver.c
2008 Oct 09
1
DO NOT REPLY [Bug 5820] New: rsync does not replace symlink atomically
https://bugzilla.samba.org/show_bug.cgi?id=5820 Summary: rsync does not replace symlink atomically Product: rsync Version: 3.0.4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: rsync@sysoev.ru
2003 Jan 18
1
possible typo/bug in receiver.c
The following code in receiver.c around line 421 (2.5.6pre1) contains some dead code: /* we initially set the perms without the setuid/setgid bits to ensure that there is no race condition. They are then correctly updated after the lchown. Thanks to snabb@epipe.fi for pointing this out. We also set it initially without group access
2004 Apr 11
1
fchmod in do_mkstemp? (patch included)
Why is do_mkstemp fchmod-ing the temporary file? I was not able to figure this out from the CVS logs or my searches in the mail archives. Currently, do_mkstemp does this (*): mkstemp temporary file (which leaves it with 0600) fchmod temporary file (final perm & 0700) And then later it gets renamed to the final name and permissions set to what they are supposed to be. (*)
2010 Jun 29
1
transfering active call to user's voicemail
Hi there, I would like to setup up my Asterisk to do this: receptionist answers the call, caller says he wants to leave a voicemail message for Ashleigh, receptionist transfers the call to Ashleigh's voicemail I guess It has something to do with dynamic features, or probably blind transfer to special ext. might do it what would you recommend? cheers!