Re: [PATCH] time limit

On Mon, 19 Apr 2004, Wayne Davison wrote: > On Mon, Apr 19, 2004 at 04:28:08PM -0400, John Taylor wrote: > > I have written a patch for rsync-2.6.1pre-2 which adds a > > --time-limit=T option. > > Thanks -- I've added it to the patches dir for now. If folks think it > is useful, it will eventual

Re: [PATCH] time limit

On Mon, Apr 19, 2004 at 04:28:08PM -0400, John Taylor wrote: > I have written a patch for rsync-2.6.1pre-2 which adds a > --time-limit=T option. Thanks -- I've added it to the patches dir for now. If folks think it is useful, it will eventually get added to the main codebase. ..wayne.. -- To un

Re: [PATCH] time limit

Oops, it looks like the pasted patch is broken, but the one on the URL is ok. http://www.terry.uga.edu/~jft/rsync-timelimit.patch.gz -John -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

[PATCH] time limit

Greetings, I have written a patch for rsync-2.6.1pre-2 which adds a --time-limit=T option. When this option is used rsync will stop after T minutes and exit. I think this option is useful when rsyncing a large amount of data during the night (non-busy hours), and then stopping when it is time f

Re: temporary file

On Mon, Apr 19, 2004 at 08:06:36AM -0600, Tim Conway wrote: > If the samba share is a bottleneck, I'd bet you'd get a big boost by > using the --whole-file option... Yes, or better yet moving the receiving rsync onto the machine that is actually storing the data. This is the only way that rsync c

Directory traversal problem.

~> mkdir -p X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X ~> rsync-2.5.6 -r X localhost:$PWD/X2 opendir(X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X/X

Re: Re[2]: temporary file

If you mean with the --whole-file, then in part, it may waste bandwidth, as any change in the files metadata will trigger a whole new send. Like I said, it depends on the nature of your data. For instance, the file you mention as an example - a .tar.gz file, will probably not have any re-usea

User configuration file

Since the RSYNCD_USERCONF resides in the user home directory isn't it more sensible to name that file dot-something ? diff -urN rsync-2.6.0/rsync.h rsync-2.6.0-new/rsync.h --- rsync-2.6.0/rsync.h 2003-12-16 23:04:59.0 + +++ rsync-2.6.0-new/rsync.h 2004-04-19 15:39:12.0 +010

Re: temporary file

no. it creates the temporary file, then deletes the old file and renames the temp file to the correct filename. Unless samba won't let you rename a file, (I know windows moves within a filesystem are copy/deletes, at least with cygwin on windows 2000), there's no actual waste there. I'd expect

Re: How to:- copy only files less / greater than X size / date?

find paths -options -print |rsync -options -files-from=- source destination The second one could easily be done with a --dry-run, preprocessing the output, and driving a --files-from= rsync with that list. Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EM

temporary file

Hello I did the following command: rsync -a --delete cpbackup /mnt/backup/ It works well, but the problem is that it seens the "temporary files" (ie: -rwxr-xr-x 1 root root 83623936 Apr 19 2004 .name.tar.gz.yGk7m7* ) are being created on /mnt/backup/ Since it's a SAMBA mounted partition, it wast

How to:- copy only files less / greater than X size / date?

Hi there, I think the subject pretty much says it all... Is this possible? I've got a couple of sites, where it would be very useful to only rsync files from the source if they are newer than a certain date, and similarly it would also be useful to only rsync certain files if they where less t