Accueil Explorer Aide
Connexion
zorun
/
kea
1
0
Fork 0
Fichiers Tickets 0 Pull Requests 0 Wiki
Aborescence: 86632c1230
Branches Tags
kea
/
src
/
lib
/
config
/
configdef.mes

configdef.mes 2.4 KB
Historique Raw

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950 
  1. # Copyright (C) 2011  Internet Systems Consortium, Inc. ("ISC")
    2. 

  2. #
    3. 

  3. # Permission to use, copy, modify, and/or distribute this software for any
    4. 

  4. # purpose with or without fee is hereby granted, provided that the above
    5. 

  5. # copyright notice and this permission notice appear in all copies.
    6. 

  6. #
    7. 

  7. # THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
    8. 

  8. # REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
    9. 

  9. # AND FITNESS.  IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
    10. 

  10. # INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
    11. 

  11. # LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
    12. 

  12. # OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
    13. 

  13. # PERFORMANCE OF THIS SOFTWARE.
    14. 

  14. 

  15. $PREFIX CONFIG_
    16. 

  16. $NAMESPACE isc::config
    17. 

  17. 

  18. % FOPEN_ERR     error opening %1: %2
    19. 

  19. There was an error opening the given file.
    20. 

  20. 

  21. % JSON_PARSE    JSON parse error in %1: %2
    22. 

  22. There was a parse error in the JSON file. The given file does not appear
    23. 

  23. to be in valid JSON format. Please verify that the filename is correct
    24. 

  24. and that the contents are valid JSON.
    25. 

  25. 

  26. % MODULE_SPEC   module specification error in %1: %2
    27. 

  27. The given file does not appear to be a valid specification file. Please
    28. 

  28. verify that the filename is correct and that its contents are a valid
    29. 

  29. BIND10 module specification.
    30. 

  30. 

  31. % MANAGER_MOD_SPEC    module specification not accepted by cfgmgr: %1
    32. 

  32. The module specification file for this module was rejected by the
    33. 

  33. configuration manager. The full error message answer from the
    34. 

  34. configuration manager is appended to the log error. The most likely
    35. 

  35. cause is that the module is of a different (specification file) version
    36. 

  36. than the running configuration manager.
    37. 

  37. 

  38. % MANAGER_CONFIG    error getting configuration from cfgmgr: %1
    39. 

  39. The configuration manager returned an error when this module requested
    40. 

  40. the configuration. The full error message answer from the configuration
    41. 

  41. manager is appended to the log error. The most likely cause is that
    42. 

  42. the module is of a different (command specification) version than the
    43. 

  43. running configuration manager.
    44. 

  44. 

  45. % CCSESSION_MSG error in CC session message: %1
    46. 

  46. There was a problem with an incoming message on the command and control
    47. 

  47. channel. The message does not appear to be a valid command, and is
    48. 

  48. missing a required element or contains an unknown data format. This
    49. 

  49. most likely means that another BIND10 module is sending a bad message.
    50. 

  50. The message itself is ignored by this module.
    51.