From: Maynard J. <may...@us...> - 2013-07-17 22:51:18
|
On 06/25/2013 09:00 AM, Maynard Johnson wrote: > Add manpage for new ocount tool > > Signed-off-by: Maynard Johnson <may...@us...> > --- > configure.ac | 1 + > doc/Makefile.am | 3 +- > doc/ocount.1.in | 224 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 227 insertions(+), 1 deletions(-) > create mode 100644 doc/ocount.1.in > [snip] > +.TP > +.BI "--time-intervals / -i " num_seconds[:num_intervals] > +Cumulative results are printed every > +.IR "num_seconds" > +instead of the default of one dump of event counts at the end of the run. > +If > +.I num_intervals > +is specified, > +.BI ocount > +exits after the specified number of intervals occur. The current behavior of ocount with the time interval option is to display running cumulative counts for each event. Some internal review comments I got indicated that it would be much more useful to show just the counts collected for each time interval. That way, it's easy for a user to take the csv brief-formatted output, paste it into a spreadsheet, create a line graph, and see how event counts vary with time. So I'm changing the code to do that. Anyone have any opinions, either for or against? -Maynard > +.br > + [snip] |