coverage: Make ovs-appctl command more useful and less alarming.
authorBen Pfaff <blp@nicira.com>
Fri, 20 Apr 2012 21:09:30 +0000 (14:09 -0700)
committerBen Pfaff <blp@nicira.com>
Thu, 26 Apr 2012 21:07:29 +0000 (14:07 -0700)
commita5f607bc8994e5ed870a62062df54e1b5753c6a2
tree24af8ed3e42f38c0a953bf9158eac700335a58ab
parent275a506cbe10db1e673fa1182582a507ba69418e
coverage: Make ovs-appctl command more useful and less alarming.

I've had a few complaints that ovs-vswitchd logs its coverage counters
at WARN level, but this is mainly wrong: ovs-vswitchd only logs coverage
counters at WARN level when the "coverage/log" command is used through
ovs-appctl.  This was even documented.

The reason to log at such a high level was to make it fairly certain that
these messages specifically requested by the admin would not be filtered
out before making it to the log.  But it's even better if the admin just
gets the coverage counters as a reply to the ovs-appctl command.  So that
is what this commit does.

This commit also improves the documentation of the ovs-appctl command.

Signed-off-by: Ben Pfaff <blp@nicira.com>
NEWS
lib/automake.mk
lib/coverage-unixctl.man [new file with mode: 0644]
lib/coverage.c
lib/coverage.h
lib/timeval.c
manpages.mk
ovsdb/ovsdb-server.1.in
vswitchd/ovs-vswitchd.8.in