Les Mikesell wrote:
v3 uses its own perl implementation to be able to compare to the
compressed archived copy.. v4 uses the server's native version.
The docs for v4 say:
* A modified rsync 3.0.9, called rsync_bpc, is used on the server
side, with a C code layer that emulates all the file-system OS calls
to be compatible with the BackupPC store. That means for rsync, the
data path is now fully in complied C, which should mean a
significant speedup. It also means many (but not all) of the rsync
options are supported natively.
Is this not correct?
Or perhaps, can v4 use either this, or the native rsync?
thanks
danno
--
Dan Pritts
ICPSR Computing & Network Services
University of Michigan
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
