Yes, I can confirm that --humanize-numbers does not affect the SIGINFO output. I have added this as an issue: https://github.com/Tarsnap/tarsnap/issues/164
I agree that it may be difficult to see progress with large files; it could very plausibly display "2.1 GB / 3.0 GB" multiple times. But I think it's less surpring to users if they see human output when they specified --humanize-numbers, rather than human output for some numbers and raw output for other numbers. Cheers, - Graham On Mon, Jun 06, 2016 at 03:21:40PM +0100, Bob Eager wrote: > Yes, but that doesn't affect the Control-T function (perhaps it > should?). > > Control-T ought, however, to show if there is ANY progress - difficult > if the numbers are humanized. > > On Mon, 06 Jun 2016 13:42:59 +0000 > Diego Veríssimo Lakatos <[email protected]> wrote: > > > Hello, I think that you are looking for the "--humanize-numbers" > > > > user@host:~$ sudo tarsnap --print-stats --humanize-numbers > > Total size Compressed size > > All archives 295 GB 220 GB > > (unique data) 8.7 GB 6.4 GB > > > > > > > > Em sáb, 4 de jun de 2016 às 19:52, Sarah Alawami <[email protected]> > > escreveu: > > > > > I forgot what signal that sends to tarsnap but is there a way to > > > humanize that set of numbers? I'm horrible with byte calculation. I > > > can approximate to a point but still. Is there a way to make those > > > numbers read a bit more friendly? With out giving the file name the > > > example would be. 4456448 / 11044528 bytes) > > > > > > Is there a way to make that look better let's say kb or even mb? > > > Depending on the number shown? I dunno if this would make > > > tarsnap consume more memory especially on slower machines or what > > > not. But just a thought. > > > > > > hope that helps a bit. Loving the program so far. > > > > > > Blessings and happy Saturday > > > >
