[bind10-dev] some stats logging comment

[Jeremy C. Reed]

 STATS_BAD_OPTION_VALUE  The stats module was called with a bad
 command-line argument and will not start.

How can a module have a command line argument?  I am curious of use case 
of this.


STATHTTPD_BAD_OPTION_VALUE

Why do we log if the stats-httpd module was called with a bad 
command-line argument? Is this logging overkill?

(Maybe it is fine to log this.)

Jelte suggested: we could probably do without the bad_option_value as 
logs, but if it prints it to stderr/stdout, boss should catch it and log 
that...  (if it doesn't right now)


STATS_STOPPED_BY_KEYBOARD probably should not be "KEYBOARD" as that is 
misleading. Should be INTERRUPT?