similar to: rsync over stdin/stdout

https://bugzilla.samba.org/show_bug.cgi?id=5220 Summary: PATCH SUBMITTED: New Feature: stdio model for client Product: rsync Version: 3.0.0 Platform: All OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

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,

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

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

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

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

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

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

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

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

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

Hi folks, Win 7 64bit R 2.12.0 32bit Problem in reading Excel spreadsheets (the text file, research_databaseI.xls, was download on Internet) > data=odbcConnectExcel(file.choose()) > sqlTables(data) TABLE_CAT TABLE_SCHEM 1 C:\\Users\\satimiswin764\\Documents\\research_databaseI <NA> 2

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've noticed a weirdness in rsync. Let me explain it briefly with an example. Below is a test script: #!/bin/sh cat >rsyncd.conf <<EOF address = localhost use chroot = no hosts allow = localhost [from] path = /tmp/from read only = yes comment = r/o EOF RSYNC_CONNECT_PROG="rsync --address=localhost --config=rsyncd.conf --daemon" \ rsync -av --address=localhost

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

I made some tests with smbclient and gzip, and it seems to me that what I'm doing should be safe, but I'd like to know if this kind of input and output redirection has some "hidden" drawbacks/problems: may it cause corruption of output files? backup: smbclient '\\server\share' -Tc - | gzip > file.tar.gz restore: gzip -dc file.tar.gz | smbclient

$ ./nbdkit ssh host=localhost /nosuchfile password=-0 --run 'qemu-img info $nbd' abc fcntl: Bad file descriptor The reason for this is that we close the file descriptor after reading the password. Closing stdin causes bad stuff to happen. --- docs/nbdkit-plugin.pod | 5 +++++ server/public.c | 4 ++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git

Take a look at the lsh scripts that come with rsync. On 10/10/2018 02:53 PM, Parke via rsync wrote: > Hello, > > Is there a way to get an rsync client to communicate over stdin/stdout? > > I found these two emails from 2004. The second email mentions that > there might be a patch. > > https://www.mail-archive.com/rsync at lists.samba.org/msg09392.html >