similar to: flist transmission and sorting

https://bugzilla.samba.org/show_bug.cgi?id=1959 Summary: writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe Product: rsync Version: 2.6.2 Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo:

Here is a diff which should allow applying batch updates remotely ( as apposed to copying the batch files to the remote server and running rsync there ). Eg rsync --write-batch=test src dst1::dst rsync --read-batch=test dst2::dst Oli Dewdney diff -E -B -c -r rsync-2.5.6/flist.c rsync-2.5.6-remotebatch/flist.c *** rsync-2.5.6/flist.c Sat Jan 18 18:00:23 2003 ---

https://bugzilla.samba.org/show_bug.cgi?id=3979 Summary: writefd_unbuffered failed to write 4092 bytes phase send_file_entry broken pipe Product: rsync Version: 2.6.8 Platform: Other OS/Version: Linux Status: NEW Severity: major Priority: P3 Component: core AssignedTo:

As you all know, rsync doesn't have any special handling for Mac OS X HFS+ resource forks. Kevin Boyd made RsyncX and rsync_hfs, to address this gap, but they only work when the destination filesystem is also HFS+. I haven't been able to find any references to an rsync that is capable of syncing from HFS+ to UFS (etc). The only solutions I've seen involve lots of preprocessing

https://bugzilla.samba.org/show_bug.cgi?id=8053 Summary: Older C compilers don't allow in-line declarations flist.c:1653 Product: rsync Version: 3.0.8 Platform: All OS/Version: FreeBSD Status: NEW Severity: minor Priority: P5 Component: core AssignedTo: wayned at samba.org

Hi, Whenever i am using the command rsync --write-batch -av --stats `cat $1` -e ssh user@remote machine:/destination/ This is writing rsync_argvs files in the home directory as well as to the destination directory. Can anyone give me any idea as how to prevent the writing of rsync_argvs files in the home directory which is of no use. Regards, Surabhi. > ---------- > From:

As those of you who watch CVS will be aware Wayne has been making progress in reducing memory requirements of rsync. Much of what he has done has been the product of discussions between he and myself that started a month ago with John Van Essen. Most recently Wayne has changed how the file_struct and its associated data are allocated, eliminating the string areas. Most of these changes have been

Hi, I am running mentioned rsync version in daemon mode on a x86 machine which is a Gentoo Linux running kernel 2.4.26 and glibc 2.3.3_pre20040207. During the sync from another machine, the rsync daemon hangs; client receives no data and server waits on select() call. when this happens, rsync server process can only be killed by SIGKILL; no timeout occurs on server side. ssh is not being used for

Steve Sills Platnum Computers, President http://www.platnum.com steve@platnum.com ----- Original Message ----- From: "Steve Sills" <steve@platnum.com> To: "jw schultz" <jw@pegasys.ws> Sent: Thursday, January 22, 2004 1:52 PM Subject: Re: Rsync's Speed > The source server is a Dual 800 Mhz /w a 7200 RPM 40 GB HDD, the dest server > is a P III 450 with a

-----Original Message----- From: Susan Ator Sent: Wednesday, March 26, 2003 12:32 PM To: 'jw schultz' Subject: RE: Logging on the rsync server from a client connect Thanks. It turns out I needed to add rsync to my ipchains. Once I did that I was able to connect correctly and log the information. I knew it was something really really basic on my end. sa -----Original Message-----

On Thu, May 15, 2003 at 10:40:21PM -0500, Lee Eakin wrote: > > Date: Thu, 15 May 2003 20:11:09 -0700 > > From: jw schultz <jw@pegasys.ws> > > Subject: [RFC] report options > > > > I have hinted in the past of wanting to go to a more > > selective control of the output of rsync. Here it is. > > > > Sounds very cool. I'm guessing that a

On Tue, Sep 16, 2003 at 03:49:45AM -0700, jw schultz wrote: > > Aside from numerous other weaknesses that have crept into > the manpage i do note that there doesn't seem to be any > point where it is mentioned that rsync replaces destination > files rather than updating them in-place. I'm not sure > where it would go in the current manpage. > > I'm no writer

Hi, I'm new to rsync and currently installing rsync-3.0.3 to a OS/390 Unix System Services environment. The build process runs fine and does not produce errors. But if I test the program, it crashes everytime with a protection exception. rsync-2.6.9 was running fine! I can't figure out why exactly it crashes. I hope that someone on this list can give me a hint on that. This is the debug

Actually, what I do also propogates deletions. Since someone may unpack a tar containing files with earlier mtimes than a marker file, a simple --newer won't do it for us, either. Instead, I generate a list of all items, consisting of name and type, to which i append number of links, size, and mtime for files; link destination for symlinks; and for directories, fifos, chars, blocks,

That's actually a very good suggestion. First I figured that in this way files changed within the hour after creation would be ignored, but they probably represent a very small minority anyway. On the other hand, this does not really rectify the situation, but will allow us to postpone the real sync again until, let's say a holiday, where we have plenty of time to sync. Rgds, Bart

On Sat, May 10, 2003 at 01:26:17AM +0200, wrote: > Hi, > > let me shortly describe the background of my problem: I was using a Gentoo box > as a workstation and a NetBSD-1.6 box as a backup machine. Everything ran > perfectly. Now I switched my workstation OS to FreeBSD-4.8_RELEASE. > > Both rsyncs are made from the ports, respectively (with Gentoo, it were the >

I just did a make clean to tidy up a bit and found four objects were missed. The seem to belong to the CHECK_PROGS set. Not sure where best to put them so created a CHECK_OBJS variable and added it to the clean rule. -- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws Remember Cernan and

On Fri, Jan 17, 2003 at 05:42:41PM -0800, Wayne Davison wrote: > On Fri, Jan 17, 2003 at 04:21:59PM -0800, jw schultz wrote: > > It should not do /root2/i386/etc/init.d/rsyncd and so on as > > -R would have it. > > -R would only do that if you actually prefixed the paths with the source > dir, which is not what happens with --files-from. The source dir is > just used

On Thu, Jan 30, 2003 at 12:19:22PM -0500, KWGworkin@aol.com wrote: > When setting up rsync in daemon mode, which side do I put the daemon on? My > environment is as follows: > > One Linux host will house the backup data files for three servers (1 SCO Open > Server and 2 Solaris 8). > > I want to know if it is better to: > 1. setup the daemon on the Linux host and push

A thought has been nagging me for a bit now so i'll run it up the flagpole and see if anyone salutes. There seems to be quite a bit of confusion regarding the use of the leading slash as a top of tree anchor for exclude patterns. The manpage seems clear enough to me but somehow it doesn't seem to get through. What if we allowed a leading circumflex (^) to serve the same function. We