Comment 1 for bug 1056838

After reviewing --run-time and --interval of these and all tools that have --run-time, my conclusion is that the option is only loosely standardized. Some tools have no default --run-time and run once then exit, others run forever. Some have a default value for --run-time. Then throw --interval into the mix and it's less standardized.

I think we should try to standardize it even more, but we can't do that for 2.1 because it would introduce a backwards-incompatability in one tool or another. So I'm going to retarget this to 2.2.