I am trying to understand how BackupPC_tarPCCopy figures out all the hard links from the PC directory to the pool without doing a lot of work and/or without caching lots of pool inodes.
I tried reading the code but I am having trouble seeing the forest for the trees. Could someone give me a high level description of the algorithm used to get around the speed/memory problem that rsync encounters when trying to deal with gazillions of hard links? The reason I ask is that I am working on an alternative approach to backing up BackupPC pc heirarchies and I want to make sure that I am not reinventing the wheel. Thanks ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
