Paul Harvey issues

Results 21 issues of


                                            Paul Harvey

snazzer* should try to read env from /etc/snazzer/snazzer.conf

expecting users to source the env on each invocation isn't terribly user-friendly

enhancement

snazzer-receive should probably take a destination directory argument

Avoid forcing cron jobs to use cd

enhancement

snazzer-measure should drop du -bs report, annotate that it's non-reproducible or replace it

The only reproducible thing would seem to be to get the number of bytes at the end of the tar operation which feeds gpg2 and sha512sum.

bug

snazzer-measure should just pgp sign the sha512sum rather than full path content

Currently the measurement reports are expensive to validate; PGP signatures are performed over the entire snapshot contents in parallel with sha512sum. It would make more sense to simply PGP sign...

snazzer usage of df --output incompatible with coreutils older than 8.23

user-submitted: won't run on systems with coreutils lower than 8.23 due to usage of `df --output`

bug

snazzer should offer --delete-all to completely cleanup after testing

Related: #4

snazzer SNAZZER_SNAPSHOTZ_PERMS should be configurable

SNAZZER_SNAPSHOTZ_PERMS=0700 is not appropriate in all cases

enhancement

snazzer-prune confusingly retains more snapshots than expected when only a few snapshots exist

This bug item is pretty much to address https://github.com/csirac2/snazzer/blob/master/doc/snazzer-prune-candidates.md#bugs-and-limitations "When some datetimes are close together, they mightn't be pruned" I've considered adding a new retention variable, SNAZZER_RECENTS_TO_KEEP - a linear...

enhancement

snazzer-prune throws uninitialized value error on empty input

Related bug: #10. user-submitted: > when doing > a dry-run on our system with no snapshots the snazzer-prune-candidates > command called by snazzer would throw an error about “Use of...

bug

snazzer --dry-run shouldn't try to create .snapshotz dirs

bug