[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Verbose mode that prints added/modified files?
- To: tarsnap-users@tarsnap.com
- Subject: Verbose mode that prints added/modified files?
- From: Simo Melenius <simo.melenius@gmail.com>
- Date: Sun, 3 Apr 2011 10:42:18 +0300
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=gnbNmYHdS0EPOCcC/5cvDNk/5om3+wOQ5vaHuJVMSInXmJ30FP9fDspj9n9/3PL0RC f4pZhdxtSUehSI1vAv/JHsdQP2vSAyYK2fL4KaPXNNXO5LjNRLmlyXf/UiR4REJOA9O4 O0EFVPjmM2QQrs3w0WA+4RDvqyrK3bm5Q4XCQ=
- Mailing-list: contact tarsnap-users-help@tarsnap.com; run by ezmlm
A quick question/feature req: When creating an archive is it possible
to print the paths of new files and updated files (that generated new
blocks on top of what was in the store already for that particular
file)?
This output would be kind of a diff to what is already stored in the
cloud. The verbose mode prints all files which isn't too useful. The
--print-stats just gives a bytes summary. I would be pretty useful to
create a new archive and see a git style list like:
- whether file is added/updated
- path
- percentage of changes vs. file size
When doing backups from my home directory, this would give me an
overview of what had changed. Ditto for logging the output of
automated backups. I can currently hack this by listing the contents
of the new and previous archive (I name them with a timestamp) and
running a standard diff between those but it's rather cumbersome (and
heavy-weight, listing files takes some time).
Would this be technically difficult considering tarsnap architecture?
I'm willing to cook up a patch for review and potential inclusion in
the upstream if it doesn't break badly against the design of tarsnap.
kind regards,
Simo
--
() Today is the car of the cdr of your life.
/\ http://arc.pasp.de/