config_messages.mes 2.1 KB

123456789101112131415161718192021222324252627282930313233343536373839
  1. # Copyright (C) 2011 Internet Systems Consortium, Inc. ("ISC")
  2. #
  3. # Permission to use, copy, modify, and/or distribute this software for any
  4. # purpose with or without fee is hereby granted, provided that the above
  5. # copyright notice and this permission notice appear in all copies.
  6. #
  7. # THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
  8. # REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
  9. # AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
  10. # INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
  11. # LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
  12. # OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  13. # PERFORMANCE OF THIS SOFTWARE.
  14. # No namespace declaration - these constants go in the global namespace
  15. # of the config_messages python module.
  16. # since these messages are for the python config library, care must
  17. # be taken that names do not conflict with the messages from the c++
  18. # config library. A checker script should verify that, but we do not
  19. # have that at this moment. So when adding a message, make sure that
  20. # the name is not already used in src/lib/config/config_messages.mes
  21. % CONFIG_GET_FAILED error getting configuration from cfgmgr: %1
  22. The configuration manager returned an error response when the module
  23. requested its configuration. The full error message answer from the
  24. configuration manager is appended to the log error.
  25. % CONFIG_LOG_CONFIG_ERRORS error(s) in logging configuration: %1
  26. There was a logging configuration update, but the internal validator
  27. for logging configuration found that it contained errors. The errors
  28. are shown, and the update is ignored.
  29. % CONFIG_SESSION_STOPPING_FAILED error sending stopping message: %1
  30. There was a problem when sending a message signaling that the module using
  31. this CCSession is stopping. This message is sent so that the rest of the
  32. system is aware that the module is no longer running. Apart from logging
  33. this message, the error itself is ignored, and the ModuleCCSession is
  34. still stopped. The specific exception message is printed.