Displaying 20 results from an estimated 400 matches similar to: "rsync - windows how should I compile the code any clues - Thanks !"
2003 Apr 17
0
rsync - windows how should I compile the code any clues -Thanks !
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
2003 Jun 12
1
questions about librsync
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
2003 Jun 08
2
state of the rsync nation? (revisited 6/2003 from 11/2000)
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,
2005 Sep 30
2
question about librsync : patch function
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
2002 Aug 04
1
MD4 bug in rsync for lengths = 64 * n
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
2003 Mar 01
2
librsync ??
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
2002 Jun 21
2
Release 3 of "rzync" new-protocol test
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
2002 Apr 24
1
[rproxy-devel] rdiff deltas not very good compared to pysync, why?
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
2005 Jul 28
1
Need help with the rsync library and the communication protocol
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
2002 Jul 31
2
new rsync release needed soon?
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
2006 Feb 22
2
[librsync-users] MD4 second-preimage attack
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
2003 Dec 19
1
Problem on XP with --delete option
Hi,
I'm experiencing a problem on rsync with the --delete option.
Situation:
Server = Mandrake Linux 9.2 running rsync daemon
Client = Windows XP workstation running cygwin + rsync2.5.1 combined with ssh.
All this implemented conform the website of Robert Scholten (http://optics.ph.unimelb.edu.au/help/rsync/)
Every thing seems to work fine exept for the --delete option.
The rsync says:
2009 Feb 27
1
rsync --files-from
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
2005 Oct 21
2
Commercial license?
Hi there
Is there a commercial license for using Rsync or the Rsync algorithm
within a commercial product? I appreciate that Rsync as it stands is GNU
and therefore it cannot be used in this way, but I thought that I would
ask the list. I understand that it is open source, but we have an
application that would benefit from something like Rsync and therefore
thought we would ask the question. If
2004 Apr 08
2
[librsync-devel] librsync and rsync vulnerability to maliciously crafted data. was Re: MD4 checksum_seed
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
2009 Jul 15
1
What happened to librsync?
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...
2011 Sep 04
5
Ranking and term proximity
Hi,
I was reading an article recently about how google ranks results
(among many other things of course) based on the proximity of the
search terms in the source documents. In addition, the position of
the search terms in the search query string itself is also taken into
consideration when determining how important each term is.
Does Xapian do something similar - at least for the first part?
2003 Apr 01
2
MD4 checksum fix
On Tue, Jan 28, 2003 at 11:22:14PM -0800, Craig Barratt wrote:
> And I have several things I would like to work on and submit:
>
> - Fix the MD4 block and file checksums to comply with the rfc
> (currently MD4 is wrong for blocks of size 64*n, or files
> longer than 512MB).
>
> - Adaptive first pass checksum lengths: use 3 or more bytes of the MD4
> block
2016 Jan 09
3
LGPL relicense port of rsync
...
> 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
> discuss such a case in an organization that contributed source code is
> nearly impossible.
>
> Looking at the source code (my short
2003 Jan 04
3
directories that change into symlinks
our daily backup is done using the rdiff-backup tool, which in turn
utilizes rsync/librsync to do the actual mirroring work.
a few days ago we did a refactoring and renamed a bunch of directories.
for backward compatibility we maintain the old names by symlinking it to
the new names. so, for example, oldname1/ now becomes newname1/, and
oldname1 is now a symlink to newname1/.
we found that