On Mon, Aug 02, 2004 at 10:54:19AM -0700, Wayne Davison wrote:
>
> - Also removed the (offset > 2*CHUNK_SIZE) check in map_ptr().
> (Did you leave this in for a reason?)
>
only because I had no idea why it was there... :)
-chris
--
To unsubscribe or change options: http://lists.samba.
On Mon, Aug 02, 2004 at 10:54:19AM -0700, Wayne Davison wrote:
> On Sun, Aug 01, 2004 at 06:16:05PM -0400, Chris Shoemaker wrote:
> > Attached is a patch that makes window strides constant when files are
> > walked with a constant block size. In these cases, it completely
> > avoids all memmoves.
On Mon, 2 Aug 2004, Wayne Davison wayned-at-samba.org |Rsync List| wrote:
> Would anyone who is seeing this problem please try out the patch that is
> attached to this bugzilla bug:
>
> https://bugzilla.samba.org/show_bug.cgi?id=1536
I gave it a test and it seems to work fine on HPUX 11.0. I
On Mon, Aug 02, 2004 at 10:54:19AM -0700, Wayne Davison wrote:
> + map = (schar *)map_ptr(buf, offset - backup, k + more) + backup;
Oops, the map length should have been extended by the value of "backup":
map = (schar *)map_ptr(buf, offset - backup, k + more + backup)
> anyone happen to know how NetApp's DataONTAP handles open files?
>
> matt
> On Aug 2, 2004, at 3:04 PM, Jim Salter wrote:
>
> > Rsync does not handle open files. Your operating system does. Either
> > the OS allows rsync access, or it doesn't. Quick crib sheet:
> >
When rsync copies a fil
anyone happen to know how NetApp's DataONTAP handles open files?
matt
On Aug 2, 2004, at 3:04 PM, Jim Salter wrote:
Rsync does not handle open files. Your operating system does. Either
the OS allows rsync access, or it doesn't. Quick crib sheet:
Normal behavior for *BSD or Linux systems: the r
Rsync does not handle open files. Your operating system does. Either
the OS allows rsync access, or it doesn't. Quick crib sheet:
Normal behavior for *BSD or Linux systems: the root user has access to
any file, at any time. Non-root users may or may not, depending on
system configuration, b
I didn't see this answered in the FAQ, and it's important to one of my
application owners.
How does RSYNC handle open or write in process files?
Thank you!
J
[EMAIL PROTECTED]
[EMAIL PROTECTED]
CONFIDENTIALITY NOTICE: This message (including any attachments) may contain Molex
confidential
Would anyone who is seeing this problem please try out the patch that is
attached to this bugzilla bug:
https://bugzilla.samba.org/show_bug.cgi?id=1536
You'll need to re-run configure and re-build before re-testing. (I
appended this patch to the bugzilla bug back on the 30th, but the
bugzill
On Mon, Aug 02, 2004 at 11:01:39AM -0600, Brashers, Bart -- MFG, Inc. wrote:
> If it's easy, maybe this would be a good addition to rsync --stats. List
> the size of the files deleted, and perhaps the net change in disk usage.
Yes, an addition like that sounds like a good idea to me. It will
req
On Sun, Aug 01, 2004 at 06:16:05PM -0400, Chris Shoemaker wrote:
> Attached is a patch that makes window strides constant when files are
> walked with a constant block size. In these cases, it completely
> avoids all memmoves.
Seems like a good start to me. Here's a patch I created that also mak
Is there a way to get rsync to estimate the net change of disk space usage
for a transfer? I can get the gross amount of files to be transferred using
"--stats", and if I use "-v" I can see a list of files to be deleted. But
then I'd have to mangle the filenames to the target path (prepend some
One comment on eliminating the read-behind in map_ptr():
The sender's read pattern can jump back a blocksize or so when it is
scanning the file using the rolling checksum and it needs to send out
the just-passed data that it didn't find a match for. We don't want
this data to be re-read from disk
13 matches
Mail list logo
