[bind10-dev] What to do with -v flags

Michal 'vorner' Vaner michal.vaner at nic.cz
Fri Jan 18 13:07:35 UTC 2013


Hello

We probably should discuss what we do with the -v switches some of our binaries
have. I guess they generally don't work since our switch to logging (which
turned out to be the case with msgq now). I see two possibilities:

Get rid of them
===============

Most of the binaries aren't meant to be run by hand anyway, so they are useless.
And it's less work.

Make them work
==============

We first need to agree on what they would actually do. Would they override the
logging configuration somehow? For how long (forever, one session, until the
logging configuration is loaded)? Should they just increase the verbosity, or
tweak the output destinations too? It would make sense to leave the file/syslog
logging on its own severity, and add another output with DEBUG to stdout. But
that's not supported by the logging library (having two destinations with
different severities) and we would need some magic to not get overwritten by
configuration updates (some support directly in the logging library that would
merge the configuration with presence of -v switch?).

Or, should we have support for some kind of temporary (single-session)
configuration overlay?

With regards

-- 
The difficult we do today; the impossible takes a little longer.

Michal 'vorner' Vaner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <https://lists.isc.org/pipermail/bind10-dev/attachments/20130118/5f1097dc/attachment.bin>


More information about the bind10-dev mailing list