Displaying 20 results from an estimated 1000 matches similar to: "[PATCH] Inplace option for rsync"
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 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 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
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
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
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.
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
2004 Feb 09
1
[patch] Add `--link-by-hash' option.
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.
Anyone have an example of an MD4 collision so I can test that case? :)
Patch Summary:
-1 +1 Makefile.in
-0 +304 hashlink.c (new)
2003 Nov 17
0
[PATCH] --source-filter && --dest-filter for rsync 2.5.6
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
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.
(*)
2003 May 20
0
patch for better handling of write failures (disk full)
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
2009 Oct 15
1
PATCH: --write-devices to allow synchronising to a block device
Hi List,
I had a need recently to efficiently synchronise between some large LUNs
(boot drive disks) at two different datacentres. Solutions like drbd and
$proprietary_array_vendors_software were overkill - we only needed
(wanted!) to periodically synchronise these LUNs whenever major changes
were generated on the source. On the other hand however, re-sending the
entire disk contents each time
2003 May 23
1
PATCH: better handling for write failures (disk full)
[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
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 Feb 01
0
Fw: Re: [Apt-rpm] I: [PATCH] 0.5.4cnc9: rsync method support
Hello,
It would be goog if attached patch will be included in upstream. This
patch adds option --apt-support for rsync and with this option rsync
will print some additiona information about file being transfered. No
program logic changed. Having this option in rsync we can have apt with
rsync method support.
Begin forwarded message:
Date: Fri, 31 Jan 2003 11:34:14 -0200
From: Gustavo Niemeyer
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
2003 Oct 06
2
Patch to revive tmpfiles
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
2004 Apr 15
0
Multiple compare-dest args
Hi all.
I have just finished a small patch that adds support for multiple
--compare-dest or --link-dest args. Its primary usage is to do incremental
backups on top of eachother. (My current backup system stores each
incremental as a single diff of the latest full.)
Example:
First full backup:
rsync -a somedir full-20040415/
First incremental:
rsync -a --compare-dest=../full-20040415 \