similar to: How to prevent batch rsync to write rsync_argvs files in the home directory

Hi all, I want to use ssh to protect my traffic, no rsh or direct rsync. But I have a problem here. Of the texts already written, I could not yet recall. Mostly they tell about success in using ssh protocol. I have made some progress by reading them, but I cannot solve the current problem, if not possibly turning to port forwarding, that is also new to me, actually. I have made two kind of

I was saddened to learn today that JW Schultz was found dead back on March 27th of this year. JW was a big help in the recent development of rsync and I sorely missed his presence during the last release cycle. JW was also the author of the Dirvish backup software, and Keith Lofstrom (who provided me with the sad news) has plans to put some memorial information onto the new dirvish site as

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

I am pleased to announce the availability of Dirvish version 1.1 final. Dirvish is a fast, disk based, rotating network backup system. With dirvish you can maintain a set of complete images of your filesystems with unattended creation and expiration. A dirvish backup vault is like a time machine for your data. New features and improvements: * Completely reworked and improved

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

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

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

I have hinted in the past of wanting to go to a more selective control of the output of rsync. Here it is. PROBLEMS with the existing --verbose et al. The simple incrementing verbose doesn't allow one to restrict stdout to what actually is of interest. For instance inside dirvish i don't care about directories, or any kind of non-regular file because they show up every time even if

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

> From: jw schultz <jw@pegasys.ws.invalid> > > On Fri, Jul 26, 2002 at 09:03:32AM -0400, Bennett Todd wrote: > >>2002-07-26-03:37:51 jw schultz: >> >>>All that matters is that we can represent the timestamps in >>>a way that allows consistent comparison, restoration and >>>transfer. >> >>A very good statement indeed. There are

> > Message: 10 > Date: Tue, 20 May 2003 17:02:35 -0700 > From: jw schultz <jw@pegasys.ws> > Subject: Re: Problem with (corrupt?) file (fwd) > To: rsync@lists.samba.org > Message-ID: <20030521000235.GB29561@pegasys.ws> > Content-Type: text/plain; charset=us-ascii > > Is it the same files each time? > What versions of rsync? > Is this over NFS? >

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

so I would check with him.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dblack face=3DVerdana><span style=3D'font-size:10.0pt;font-family:Verdana;color:black'><o:p>&nbsp;</o= :p></span></font></p> <div> <p class=3DMsoNormal =

(I'm not sending this to dirvish@pegasus because I think that this message applies more to rsync's --link-dest option than to just dirvish.) I recently noticed a huge spike in dirvish network usage and traced it to files whose permissions had been changed. (with rsync v2.5.6) I understand and agree that a --link-dest copy of a source file cannot be hardlinked to, but couldn't a

On Mar 20, 2008, at 3:00 PM, Joachim Durchholz wrote: > Hi all, > > I just forgot to ./configure with CC=gcc-4.2 CXX=g++-4.2, getting the > (broken-for-LLVM) gcc-4.1 as a compiler. > The error message that I got was this: > make[1]: Entering directory `/home/jo/llvm-wrk/lib/VMCore' > make[1]: *** No rule to make target > `/home/jo/llvm-wrk/Release/bin/tblgen',

Hi all, I just forgot to ./configure with CC=gcc-4.2 CXX=g++-4.2, getting the (broken-for-LLVM) gcc-4.1 as a compiler. The error message that I got was this: make[1]: Entering directory `/home/jo/llvm-wrk/lib/VMCore' make[1]: *** No rule to make target `/home/jo/llvm-wrk/Release/bin/tblgen', needed by `/home/jo/llvm-wrk/lib/VMCore/Release/Intrinsics.gen.tmp'. Stop.

Any feedback on this patch and the possibility of getting it into CVS or the patches directory? Thanks, Craig ---------- Forwarded message ---------- To: jw schultz <jw@pegasys.ws> From: Craig Barratt <cbarratt@users.sourceforge.net> cc: rsync@lists.samba.org Date: Sat, 01 May 2004 17:06:10 -0700 Subject: Re: setting checksum_seed jw schultz writes: > > > There was some