BIND 10 trac743, created. f5278f2ac4becb33b93dc4c2fa7e6558a7daad8f [trac743] update a doxy message

[BIND 10 source code commits]

The branch, trac743 has been created
        at  f5278f2ac4becb33b93dc4c2fa7e6558a7daad8f (commit)

- Log -----------------------------------------------------------------
commit f5278f2ac4becb33b93dc4c2fa7e6558a7daad8f
Author: Jelte Jansen <jelte at isc.org>
Date:   Wed May 11 15:28:59 2011 +0200

    [trac743] update a doxy message

commit c47f23e502e998d7885d4d3d679c1eacb1dab790
Author: Jelte Jansen <jelte at isc.org>
Date:   Wed May 11 15:22:26 2011 +0200

    [trac743] Replace direct output by liblog calls
    
    While creating messages and extended descriptions, I noticed a few potential problems, which I also fixed;
    
    - If the config manager does not accept the modules specification, or if the
      'get current config' command returns with an error, the system used to
      ignore that fact apart from printing an error, and continue running. It
      seems much better to explicitely fail, since the module would be running
      independent of what its config is supposed to be, which would be really
      unstable
    - If the module cannot parse a command it gets over the command channel,
      it used to send back an error. If we have multiple modules listening on
      the same channel, this would result in multiple errors being returned
      It will now log an error, but it will not send back an answer

commit 6fc6ecda47f8556fc0a4daabc042b0b1a2d7d592
Author: Jelte Jansen <jelte at isc.org>
Date:   Tue May 10 16:20:23 2011 +0200

    [trac743] Initial addition of (empty) .mes file

-----------------------------------------------------------------------