similar to: rZync 0.08 released

For anyone who'd like to check out the latest release of my "rzync" [sic] test release, I've just released a new version. For those that might not have time to look at the code but could provide some feedback based on a rough description, I've created the following simple web page: http://www.clari.net/~wayne/new-protocol.html Here's the tar file of the new

I've been having a lot of fun improving my new-protocol testing app. It's seems to be in pretty good shape (for test code), so I figured I'd announce another release for those brave souls that may want to help me in my thinking about a (potential) new rsync protocol. It's a tar.gz file this time because I broke up the code into multiple files. I named it "rzync" just

For the small number of people who are checking this out, I released version 0.05 a couple days ago (and only mentioned it on my new-protocol web page) followed today by 0.06. Some highlights of the two releases: - We handle symlinks now in our recursive synchronization mode. - Directory scanning is no longer limited to one active directory at a time (which was sorely needed when all the

I found some time in the past week to work on a simple test app that would hopefully help to answer a few questions that came up recently: 1. Can a single-process generator+receiver work well? (Looks good so far, but I haven't run any multi-processor timing tests yet.) 2. How easy is it to use librsync? (Pretty easy.) 3. How small would a transfer-only tool be? (It's currently

Hi, I've been trying to use rsync to backup the content of a large web application on our Digital unix servers. I'm having some success but the main problem is the sheer number of files and subdirectories which must be copied/maintained between the two servers (one is our standby system). Believe it or not there are in excess of 7.5 million files/directories which must be synced between

Hi, I am working on a replication tool for lustre filesystems. We have introduced a mechanism for getting the changes that have been made to a lustre filesystem - similar to inotify. We call this mechanism, changelogs. For performing replication, we open the source file using its 'file identifier' or FID (think of it an inode that is unique cluster wide) instead of its path. The file is

Hi. It seems that librsync got left by the roadside ... is there anything similar for rsync 3.x.x? Or, is there any easy way to use the library routines in the rsync 3.x.x source independantly? The only other open source software I've found that looks similar is xdelta, and it's still beta for v3.x Thanks, Sam -------------- next part -------------- An HTML attachment was scrubbed...

Hey, I'm currently adding rsync to pacman (http://archlinux.org/pacman). A static version of the program is used for rescue operations. Because of this it is impossible to use the rsync client programm via an execve call and we need a version implemented in C. So I started implementing it. But the rsync source isn't beautiful or structured - it's just a big hunk of code. I spent

Thanks Donovan, I downloaded the librsync 0.9.6 from sf and it compiled just fine believe it or not in the new visual studio.net. There where warnings but no fatal errors and the exe seems to be running just fine. I've tested it just now on a 60 meg mdb file that I've been trying to backup.. it seems to work great!. I even saved the original so I could apply patches and then file compare

Didn''t have quite enough space to describe it there...basically i''m having a problem with the :uniq option in my tags. I''m using acts_as_taggable_on_steroid which adds these associations to my Resource class: Resource has_many :taggings, :as => :taggable, :dependent => :destroy, :include => :tag has_many :tags, :through => :taggings, :uniq => true

I'd like to revisit the topic of moving files from system to system using rsync. I've just updated my patch from its 2.5.0 version to 2.5.1, and I'm curious what people think about getting it integrated into rsync. The patch comes in two parts. The first eliminates a potential hang condition that can happen if the data channel from the receiver to the generator gets clogged up.

There's a program to apply patches, typically called "patch" Try "man patch". If your system doesn't have, and can't get patch, just read the patches and edit the appropriate files by hand. It's not particularly difficult. Incidentally, I want to point out that there's no good reason to cc rsync-admin@lists.samba.org on a regular post. I've been

Hi! I've been looking for a solution to periodically pull files from a server and delete them after a successful download. rsync + the --move-files patch seems to be the perfect solution for it as I can run it through ssh. I've found the following download location in the mail archive: http://www.clari.net/~wayne/rsync-nohang.patch http://www.clari.net/~wayne/rsync-move-files.patch

Hi, from my point of view: On Sat, 9 Jan 2016 14:48:09 +0100 Per Lundqvist <perlundq at gmail.com> wrote: > ... > > Getting the approval for a relicensing I think the contributions to > > rsync have to be analyzed in detail to approach a reasonable number of > > contributors. > > > > I experienced that finding a responsible person that is willing to >

I am the author of BackupPC (http://backuppc.sourceforge.net) and I am working on adding rsync support to BackupPC. I am implementing the server-side in perl, and the client will run vanilla rsync. (BTW, is there the protocol documented? I've answered all my questions by looking at the source, but it would be great to check against any docs.) I started with librsync 0.9.3 and the

I found the cvs repository at = http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/librsync/librsync/ The sourceforge project was just setup a couple of days ago. That must have = been why google could not find it yesterday. I believe the samba cvs site for librsync is now deprecated. The 0.9.5.1 version I was looking for looks to me to be a Jun. 27 cvs snapshot = from wherever cvs was at that

On the subject of needed patches, I just recently completed a patch for librsync that fixed the mdfour code to have uint_64 or 2 uint_32's for size. Without this, the checksums on files >512Megs are incorrect. The code should drop into rsync without a hitch. The same goes for mdfour in samba, becuase that is where librsync got the code from anyway. Robert Weber University of

I'm not sure if this is the appropriate forum for questions regarding librsync, but couldn't find any others. I'm trying to get librsync working properly on Solaris 2.7 and 2.8 Sparc servers. The problem is that while librsync appears to compile cleanly, "make check" fails the sources.test. Does anyone have any insight as to why this might be? Might I need a specific

On Thu, 2004-04-08 at 12:36, Martin Pool wrote: > On 5 Apr 2004, Donovan Baarda <abo@minkirri.apana.org.au> wrote: > > > librsync needs a whole file checksum. Without it, it silently fails for > > case 1), 3), and 4). > > Yes, a whole-file checksum should be used with it. Presumably > something stronger than md4 like SHA-1. md4 is probably good enough for most

Hi Donovan, Thank you for the insight. I will keep you posted on this. Best Regards Naveen A. >From: Donovan Baarda <abo@minkirri.apana.org.au> >To: Naveen Athresh <naveenathresh@hotmail.com> >CC: rsync@samba.org,librsync developers list ><librsync-devel@lists.sourceforge.net> >Subject: Re: rsync - windows how should I compile the code any clues >-Thanks