Closed geoffreywiseman closed 11 years ago
It seems like quiet categories, already created, does a good job with this -- if you're going to be doing a regular batch prune, use quiet categories for things you don't want to log, and then if you need to do a manual diagnosis, turn on --verbose.
What I need to do here, is customize the retention policies in our environments to be quieter and verify that these controls do enough for what I need.
Realized I could easily deal with this using a release candidate build of v1.2.
Published rc3, testing it out -- will review the logs from the server after a couple of days.
One of the two directories was being pruned with --verbose, which is an obvious problem for reduced-output. Also, .prune was being analyzed. Fixed the former, filed an issue for the latter.
The output volume looks a lot better now. I'd still like a log-style output option, but that's a job for another release.
When you're doing batch execution of prune, getting the long list of categorized files is overkill. Would be nice to reduce the output significantly, although getting the right level of detail is important here. Maybe don't show files that you're going to retain?
Alternately, perhaps you change the existing summary messages to print out the files deleted? Anyway -- not sure exactly what the implementation choices would be, but a quieter summary for batch execution would be nice, as the existing output is a little spammy for a log file, although well-suited for interactive mode.