I've run out-of-space quite a few times recently, so I have been manually
deleting some old daily backup sessions, then editing the vault's
dirvish/default.conf file. This sloppy technique opens free space quickly,
but it usually involves having to do a few more manual deletes before my
adjustments become stable. When my dataset grows significantly, I will have
to do it all again in a couple of months. When I go on vacation next month,
my assistant administrator will be doomed!
I *REALLY* need to buy and mount more disk space, but I don't have the
budget or time for that project this quarter.
I saw the "dirvish-expire --time time_expression" command, but that doesn't
accelerate the expiry of existing backups, either.
I know how to edit dirvish/default.conf, but I would like to make a script
to edit the Expire: lines in all the sessions in a given vault so that
present and future backups will expire a day or two earlier.
Image-now: 2007-05-10 02:57:47
Expire: +21 days == 2007-05-31 02:57:47
Does dirvish-expire look at the right-most fields on the Expire line, or
does it look at the Image-now: line and add "+21 days?" If the "+21 days" is
just for human eyes, is there any harm in editing the latter date stamp
alone? I've tried tracing the Perl code of dirvish-expire to learn some
more, but Pegasystems Technologies and J.W. Schultz were just a whole lot
more sophisticated programmers than I am. (Dammit, Jim! I'm a shell
scripting dilettante, not a serious Perl hacker....)
I was thinking about using sed in a script to change the Expire line, but my
code got really ugly when I went over an end-of-month break (don't even ask
me about leap-year handling!)
Surely I can't be the first person to have wanted this functionality. Does
anyone else out there have a suggestion to simplify my life?
-dP
_______________________________________________
Dirvish mailing list
[email protected]
http://www.dirvish.org/mailman/listinfo/dirvish
