Patch to change verbose level of a running app.

[cizek@…]

The attached patch allows you to change the VERBOSE level of mythbackend or mythfrontend while it is running.

It works as follows:

mythbackend --setverbose record,network

is similar to starting mythbackend -v record,network, but will make the change to the currently running mythbackend instance.

For mythfrontend, this is changed by the network control interface using "query verbose" and "setverbose {verboselevel}" as follows:

MythFrontend Network Control
Type 'help' for usage information
---------------------------------
# query verbose
 important general pthread
# setverbose playback
OK
 Previous filter:  important general pthread
      New Filter:  important general playback

# 

This was done against 0.21-fixes. Hopefully it will work with trunk also.

-Bill

[cpinkham]

(In [21396]) Add the ability to change the verbose level of a running mythfrontend and master mythbackend.

To change a frontend's verbose level, connect to the telnet/networkcontrol interface and issue "set verbose DEBUG-LEVEL" where DEBUG-LEVEL is the same list of network,database,upnp etc. that you can use from the command line with "-v".

To change the master backend's verbose level, run "mythbackend --setverbose DEBUG-LEVEL" where DEBUG-LEVEL is that same set of items that you use with "-v".

The change either back to the default debug level (currently "important,general") use the word "default" for the DEBUG-LEVEL.

Closes #6190 using a modified patch from Bill Cizek.

[cpinkham]

(In [21397]) Build on [21396] a little bit. This patch changes the 'default' debug level to be whatever level the mythbackend/mythfrontend was started with. So, if you startup the backend with "-v none", then turn on network debugging with "--setverbose network", you can later revert back to the original level of 'none' by issuing "-v default".

References #6190.

[cpinkham]

(In [21417]) Rework [21396] a little to move the VERBOSE message that shows the new verbose level outside of parse_verbose_arg(). This fixes an issue with the verbose level message being printed out before the command line arguments had been fully evaluated which could mean this message would be printed to stdout when the user wanted all output to go to a log file.

References #6190.