Am 11.11.2012 um 02:33 schrieb Antonio Diaz Diaz:
> But I think I can make ddrescue more robust by "fixing" this "problem"
> because it is easy to readjust ddrescue at no cost so that it continues
> updating the progress with inaccurate rates but accurate sizes.
>
> Of course, someone will then complain about wrong rates when he changes the
> date. ;-)
Why not really fix it by switching all relative timing to
std::chrono::steady_clock?
As a bonus the accuracy of the reported current rate would benefit from a
resolution <1s – especially for cluster sizes that typically have a read time
of a few seconds.
Greetings,
Florian
_______________________________________________
Bug-ddrescue mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-ddrescue
