also sprach martin f krafft <madduck AT madduck DOT net> [2010.08.28.1718 
+0200]:
> This is in contrast to what I am experiencing. Is backuppc fetching
> the file into memory to compare it with the pool from there?
> 
> Thinking about it, this is what needs to happen because it needs to
> have the file to determine its hash.
> 
> But shouldn't it just need to transfer the 1st and 8th 128k chunk to
> determine the hashing? Or is is that hashing function only used once
> the whole file has been transferred?

Using lsof, I found that the BackupPC_dump process actually has the
corresponding pool file up for reading, so it has identified it.

This makes me wonder even more why the client still transfers the
whole file. Shouldn't BackupPC_dump terminate the transfer and
procede to the next file instead?

-- 
martin | http://madduck.net/ | http://two.sentenc.es/
 
"never try to explain computers to a layman.
 it's easier to explain sex to a virgin."
                                                    -- robert heinlein
 
(note, however, that virgins tend to know a lot about computers.)
 
spamtraps: madduck.bogus AT madduck DOT net

digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)

------------------------------------------------------------------------------
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d

_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/