[bind10-dev] Task 1005 - Check Logger Names in cfgmgr

[Michal 'vorner' Vaner]

Hello

On Mon, Jun 27, 2011 at 03:55:45PM +0100, Stephen Morris wrote:
> A solution that occurs to be that should be simple to implement
> (although not very elegant) is to maintain a list of valid logger names,
> and check against it both when creating a logger and when configuring one.
> 
> The list doesn't have to be a text file - it could be some hard-coded
> list of names in the liblog library with an interface to access it from
> both C++ and Python.  Of course, the list would need to be updated every
> time a new logger was added to the code, but that is unlikely to be a
> common occurrence.

That sounds error prone to me. But I see another problem. We currently can do
these things from the configuration plugin:
• Return a hard-error. This suggests it should be a warning.
• Log a message, which is not presented right away to the administrator sitting
  at cmdctl.

So, even if we go with the non-system solution (which might be the best thing
for now), we need a way to push the warning all the way trough multiple
interfaces to the config manager. That sounds nontrivial to me.

And if we want to have some way to guess the list at runtime, we would better
solve the problem with offline configuration first.

With regards

PS: Apologies to Stephen for duplicity, I forgot to CC the list the first time.

-- 
do { goto Water; } while( !tryBreakOffTheHandle() );

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