high CPU usage with TAR files

2007-10-09 Thread James V
I am trying to use rsync to backup our Linux server and when the rsync is running it uses 1-2% CPU for most operations until it reaches a tar file (or another file archive), then the CPU usage increases to 90%. I am assuming that rsync is looking at the individual files in the tar archive and

patch for rsync: provides nice = N option

2007-10-09 Thread Steve Friedl
Hi folks, This is a patch for rsync 2.6.9 - I'm not sure if this is the proper vehicle for submitting them. It's been working great for us for months, and I hope it's seen as offering useful utility in general. Steve (who is not a subscriber to this list) --- Stephen J Friedl | Security

Recognizing directory name changes

2007-10-09 Thread Frank Thomas
I've decided to proceed down another path to solve this problem, at least until rsync is able. I've begun to code a perl script that keeps a lookup list of file and directory names to inodes. What will occur is the pointer list check will be run just before the rsync job and perform name changes

Re: Recognizing directory name changes

2007-10-09 Thread Matt McCutchen
On 10/9/07, Frank Thomas [EMAIL PROTECTED] wrote: I've decided to proceed down another path to solve this problem, at least until rsync is able. You aren't happy with --detect-renamed ? Is there any way to change the dry-run option to display a probable transfer size if the command was run.

Re: high CPU usage with TAR files

2007-10-09 Thread Matt McCutchen
On 10/9/07, James V [EMAIL PROTECTED] wrote: I am trying to use rsync to backup our Linux server and when the rsync is running it uses 1-2% CPU for most operations until it reaches a tar file (or another file archive), then the CPU usage increases to 90%. I am assuming that rsync is looking

CVS update: rsync/patches

2007-10-09 Thread Wayne Davison
Date: Tue Oct 9 06:17:07 2007 Author: wayned Update of /data/cvs/rsync/patches In directory dp.samba.org:/tmp/cvs-serv29991/patches Modified Files: dynamic_hash.diff Log Message: Improved to avoid a hashtable slowdown for files that don't need the extra-large hashtable. Revisions: