similar to: What happened to librsync?

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

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

I'm interested in these very questions (librsync-rsync relationship, remaining limitations of rsync, active prospects for ground-up rewrites), Google searches for rsync info have proved a little too vague due to the programs ubiquity. Much has certainly changed since this was written, could some people with knowledge in these areas could update martin's response for the state of rsync,

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

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

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

Hello everybody, About librsync, does anyone know how to patch the delta without creating a new file ? I used the librsync and it always generates a new file, which is embarrassing if the file is over 1Gb. I tried to store the new file in RAM, but it saturates the machine. Is there a possibility to write in the current file to be synchronized, although this file is currently being

All, Does anyone know anything about librsync, and where it is currently maintained = on the web? It apparently is/was a samba project, but I'm not sure how it relates. The authors are listed as: Martin Pool <mbp@samba.org> Andrew Tridgell <tridge@samba.org> but I suspect someone else did the 0.9.5.1 update, because only 0.9.5 is = available on the rproxy site

On Tue, 2006-02-21 at 14:58 -0800, rsync2eran@tromer.org wrote: > A year ago we discussed the strength of the MD4 hash used by rsync and > librsync, and one of the points mentioned was that only collision > attacks are known on MD4. Could you please forward this into the bug tracker so it's not lost? -- Martin -------------- next part -------------- A non-text attachment was

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

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

I'm working on a commercial project that would benefit immensely from the use of rsync. However, I cannot convince management that rsync is a worthy tool due to the rote "it's shareware, it's not supported" FUD. Are there any documented, corportate users of rsync? Testimonials? In short, how do I drag this risk-averse group out of the FTP age into the rsync present? /p

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 librsync 0.9.5 is released from rproxy.samba.org. This release contains small but important bug fixes. Changes in 0.9.5: * Bugfix patch from Shirish Hemant Phatak MD5 checksum: df1c35520e4b0bf9d6d7ac813ba86a14 *librsync-0.9.5.tar.gz - -- Martin Pool -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see

On 24 Apr 2002, "Shirish H. Phatak" <shirish@tacitnetworks.com> wrote: > Since there appears to be a dedicated group of users and lots of > activity, maybe we can convince Martin to roll in these patches and make > a new release? I have been really lax in supporting librsync for the last few months, because of a new job and taking over maintenance of rsync

I've released the next version of my rZync test app. You can find a link to it here: http://www.clari.net/~wayne/new-protocol.html You should also snag the referenced librsync source, as some important bugfixes in librsync are needed to compile rzync. For those that don't know, rZync is my new-protocol test app that I'm using to try out some ideas on how to improve the rsync

Hi, Is there a way in which rsync's -z compression (zlib) utility can be benchmarked? I'm trying to compare the compression ratio between rsync and external compression tools like gzip and bzip2. Are there any advantages to using rsync's internal compression mechanism specified with the -z option compared to solely applying external compression i.e. bzip2 to the files and invoking

I'm trying to use the rsync algorithm for incremental backups. After a quick look at rsync I saw the batch mode operations, and I thought that maybe I can modify them for incremental backups. What is needed is to add an option to save the checksums of all the files of the level 0 backup and a second option to use the level n checksum to calculate the delta batch files for the level n+1

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've been researching the state of 'file alteration monitoring' technology on Linux. Famd uses dnotify to inefficently monitor a handful of directories. The replacement for dnotify is being worked on in the kenel and it's called inotify. If I understand it correctly and they get it finished, it would be an awesome addition to rsync. With it, you could run rsync to update a