On Wed, Feb 06, 2008 at 02:20:09PM -0500, Paul Fox wrote:
> Robin Lee Powell <[EMAIL PROTECTED]> wrote:
>  > On Wed, Feb 06, 2008 at 09:33:47AM -0800, Robin Lee Powell
>  > wrote:
>  > > This reminds me: is there some fundamental reason backuppc
>  > > can't use symlinks?  It would make so many things like this
>  > > *so* much easier. It such a great package otherwise; this is
>  > > the only thing that's given me cause to be annoyed with it.
>  > 
>  > Still wondering this.
> 
> with hard links, you can tell that a file in the main pool is no
> longer needed, by looking at its link count.  when the link count
> goes to 1, none of the per-PC backup trees is referencing it, so
> it can be deleted.  (this is what the BackupPC_trashClean process
> does.)
> 
> with symlinks, you wouldn't get that reference count, and "garbage
> collection" would be much more expensive.

I'd happily pay the price in garbage collection to have something
that could be remote mirrored easily.  Judging by the number of
requests this mailing list has had for such a feature, I'm not the
only one.

I'd even be willing to put some money forward if someone wants to
code this feature; I'd rather not dig into backuppc's code if I can
avoid it.

Having options to easily allow backuppc to encrypt the pool while it
compresses would also be wonderful.

-Robin

-- 
Lojban Reason #17: http://en.wikipedia.org/wiki/Buffalo_buffalo
Proud Supporter of the Singularity Institute - http://singinst.org/
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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/

Reply via email to