similar to: rsync - windows how should I compile the code any clues -Thanks !

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, I have a unique issue that I am dealing with here. I need to develop rsync algorithm into a library that can be re-used with my VB / VC application on Windows platform. I need your advice if there is any library already available on the Internet for this? I did get librsync but that is just a header file which I do not know how to compile also with the existing code I have. Can you

G'day, I've been working on a Python interface to librsync and have noticed that it uses md4sum code borrowed from Andrew Tridgell and Martin Pool that comes via rsync and was originally written for samba. Is there anything special about this code compared to the RSA md4sum code that can be found with libmd <"http://www.penguin.cz/~mhi/libmd/">? Python uses the RSA

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

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

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 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 version 2.6.0 of rsync. Two important things to note in the new release: 1. The default remote shell is now "ssh" unless you tell the configure you want to use something else. 2. Some bug fixes in the include/exclude code, while making things work properly, have resulted in some user-visible changes for certain wildcard strings. Read the

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 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

2000) into dos, and with your boot disk, read the share listing of machine A from a linux box and mount it, and the rsync the whole drive if shared (say c:\ with c:\winnt and all the good stuff). Though, i still could NOT actually restore this 'mirror' image like i could a 'mirror' image of a linux root?? So, ultimately, there is no reason to even waste the hard-drive space

Hi, The following lines in compat.c are rather imprudent: if (read_batch || write_batch) checksum_seed = 32761; else checksum_seed = time(NULL); write_int(f_out,checksum_seed); Setting checksum_seed to a constant in batch mode means block collisions are reproducible and predictable. Thus, some files will be permanently "unlucky" in batch mode and will

https://bugzilla.samba.org/show_bug.cgi?id=12781 Bug ID: 12781 Summary: rsync library Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: core Assignee: wayned at samba.org Reporter: ildar at altlinux.ru

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

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

-----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

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 >

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

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