similar to: FWD: Re: specifying a list of files to transfer

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:

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

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

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

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,

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

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 Thu, Aug 28, 2003 at 12:51:16PM +0300, Sviatoslav Sviridov/Lintec Project wrote: > > Sorry for direct reply, but mail server at samba.org blocks my messages. Postmasters, Martin, For your consideration. > Begin forwarded message: > > Date: Thu, 28 Aug 2003 12:43:54 +0300 > From: Sviatoslav Sviridov/Lintec Project <svd@lintec.minsk.by> > To: rsync@lists.samba.org

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

Wayne, I've been ruminating a bit on the qsorted flist and duplicate removal and have an idea. What if we removed end_file_entry() from send_file_name() and instead had a for(i=0; i < flist->count; ++i) send_file_entry(flist->files[i], f, ??) in send_file_list(). As near as i can tell this would be unnoticeable to the protocol. Once done the sort of the file list could be

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

Hit the "not a regular file (recv_files)" error last night having replaced a directory with a file. The really dumb part is that this was hit doing a link-dest on an empty destination so the robust_unlink would have presented no problem anyway. I can see no reason why non-directory special files should have any problem being replaced so i've changed that logic too. The new code

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 >

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

This patch causes --exclude-from and --include-from to read from STDIN when given - for a filename. This was formerly incorporated in my --link-dest patch. Patch against current cvs. -- ________________________________________________________________ J.W. Schultz Pegasystems Technologies email address: jw@pegasys.ws Remember Cernan and Schmitt -------------- next part

This is just a trivial documentation change. The word "link" is overloaded. It refers to symlinks, hardlinks and network links. When looking for references to file links in the manpages the network references get in the way. This patch changes when reasonable to do so the word "link" to "connection" when referring to the network. This is just a suggested

On Mon, Jun 02, 2003 at 03:32:04PM -0700, Michael Rubel wrote: > Hi J.W., > > Please pardon this intrusion on your private address; the rsync list seems > to be down (no messages since yesterday), so I'm forwarding this directly > to you. If you'd rather wait until the list restarts, that's fine too. I'm CCing the list. > > Best regards, > Mike >

On Mon, Jun 23, 2003 at 11:12:03PM -0400, Stephen Gildea wrote: > I have a suggestion for how to make the documentation of rsync's > "--compare-dest" option clearer. > > Maybe it would be clearer if I had some problem this option would solve, > but as it is, I couldn't figure it out from the manual. The description > in the rsync 2.5.6 manual page starts:

On Mon, Dec 15, 2003 at 10:51:08AM -0800, Wayne Davison wrote: > On Mon, Dec 15, 2003 at 10:03:28AM -0800, jw schultz wrote: > > > The one thing i really would have liked to have seen in a version bump > > would have been changing the default remote shell to ssh instead of > > rsh/remsh. > > I can see this being both a good thing (since I think it is a better >

I just reviewed the EXCLUDE PATTERNS section of the manpage and found that the declarative portion never actually states that only the part of the path that is relative destination is compared. I'm not quite satisfied with my text on this so if anyone has a better way of stating it i'm open to suggestions. Index: rsync.yo