similar to: Delta-compression and --write-devices

Greetings, I am using cygwin/rsync to backup windows data to a linux server. I recently upgraded an implementation of rsync from 2.6.8 to 3.0.4 and have encountered a problem. In the previous version of rsync a /./ in the from file would cause the previous path information to be dropped for the destination directory. In 3.0.4, it appears the . is being translated into the current (working)

Hit the "not a regular file (recv_files)" error last night having replaced a directory with a file. The really dumb part is that this was hit doing a link-dest on an empty destination so the robust_unlink would have presented no problem anyway. I can see no reason why non-directory special files should have any problem being replaced so i've changed that logic too. The new code

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

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

Currently orphan cleanup only ever gets triggered if we cross subvolumes during a lookup, which means that if we just mount a plain jane fs that has orphans in it, they will never get cleaned up. This results in panic''s like these http://www.kerneloops.org/oops.php?number=1109085 where adding an orphan entry results in -EEXIST being returned and we panic. In order to fix this, we

Hi, In 3.0.4, encountered a problem with dot-dir path (e.g. , foo/./bar) inside a -files-from file when the root of the transfer isn't in the current directory. This was fixed in 3.05 (well, partially). 3.0.5 bug fixes release info: - Fixed the use of a dot-dir path (e.g. foo/./bar) inside a --files-from file when the root of the transfer isn't the current directory.

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.

https://bugzilla.samba.org/show_bug.cgi?id=12527 Bug ID: 12527 Summary: Sender waits for timeout when fuzzy basis file found Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 Component: core Assignee: wayned at samba.org

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

https://bugzilla.samba.org/show_bug.cgi?id=6116 Summary: Cannot access files in exposed shadow drive in version 3.0.5 Product: rsync Version: 3.0.5 Platform: x86 OS/Version: Windows NT Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

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 \

Hello! I have a matrix with data and a column indicating whether it is censored or not. Is there a way to apply weibull and exponential maximum likelihood estimation directly on the censored data, like in the paper: Backtesting Value-at-Risk: A Duration-Based Approach, P Chrisoffersen and D Pelletier (October 2003) page 8? The problem is that if I type out the code as below the likelihood

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

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

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

Hello, here is a preliminary patch allowing rsync 2.5.6 to compile in BeOS (using the new BONE networking stack). Some explanations: - BeOS doesn't have chroot(), - the BONE networking stack export legacy network function for old apps in libnet.so (linked to by default), so it's necessary to force linking to the new libraries for things to work. I've yet to get inet_ntop() to be

Some background: I have been assigned a task to implement one-way synchronization of a large file storage to another box. The problem is that on the target box a special directory has to be maintained in which symlinks to received files should be created using special logic. After some experimentation I have set up a named pipe which is used by the receiving rsync daemon for transfer logging;

Peter, I was about to post the below to the rsync mailing list, but wondered whether your code which captures rsync output may have allowed rsync to continue past what I think would normally be a fatal error? Thanks Rob. P.S. Should I put the final backups of the old pearcey /home back into their correct slots - 5 backups were recycled, but nothing was added to them? The .Snapshots area is

Hi R users, I am working with the fda package but when I call the function pca.fd I obtain a message error, which I cann't identify. The error say That : error in assihn(mname,def,where), is not possible to add links to a blockade enviroment. The orther that I'm writting is: > cp1 <- pca.fd(ind.fd1,nharm=3) and before it I can to plot the functional data object ind.fd1. ?Have

Recently various needs for multiple version handling were discussed and I put forward a plan of mine. Subsequently the proposal for a --compare-file=<FILE> switch had support, so I have implemented this. I have also implemented an experimental --compare-auto which decides which file to match against using a rule. Instructions for patch: 1. Install rsync-2.5.6 source 2. "patch -p1