On 3/16/11 2:28 PM, Paul Slootman wrote: > Of course, if someone wants to code something up for this situation, > I'd not have any problems with such a feature; as long as it's well > documented (and perhaps made optional?).
I wouldn't object to another stand-alone maintenance program, which I could choose to run before dirvish-expire, which would attempt to determine if some backups were more valuable than before and change their expiry date to well in the future. It could be triggered by finding runs of failed backups, backups where more than a normal percentage of the files have changed, etc., etc. The biggest problem I see is translating the "just do what I mean" heuristics into algorithms that a significant percentage of dirvish users can agree on. ;-) -- --Jon Radel [email protected] _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
