Home Explore Help
Sign In
zorun
/
kea
1
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: 4903410e45
Branches Tags
kea
/
src
/
lib
/
asiodns
/
asiodef.msg

asiodef.msg 2.8 KB
History Raw

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556 
  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 ASIODNS_
    16. 

  16. $NAMESPACE isc::asiodns
    17. 

  17. 

  18. FETCHCOMP   upstream fetch to %1(%2) has now completed
    19. 

  19. + A debug message, this records the the upstream fetch (a query made by the
    20. 

  20. + resolver on behalf of its client) to the specified address has completed.
    21. 

  21. 

  22. FETCHSTOP   upstream fetch to %1(%2) has been stopped
    23. 

  23. + An external component has requested the halting of an upstream fetch.  This
    24. 

  24. + is an allowed operation, and the message should only appear if debug is
    25. 

  25. + enabled.
    26. 

  26. 

  27. OPENSOCK    error %1 opening %2 socket to %3(%4)
    28. 

  28. + The asynchronous I/O code encountered an error when trying to open a socket
    29. 

  29. + of the specified protocol in order to send a message to the target address.
    30. 

  30. + The the number of the system error that cause the problem is given in the
    31. 

  31. + message.
    32. 

  32. 

  33. RECVSOCK    error %1 reading %2 data from %3(%4)
    34. 

  34. + The asynchronous I/O code encountered an error when trying read data from
    35. 

  35. + the specified address on the given protocol.  The the number of the system
    36. 

  36. + error that cause the problem is given in the message.
    37. 

  37. 

  38. SENDSOCK    error %1 sending data using %2 to %3(%4)
    39. 

  39. + The asynchronous I/O code encountered an error when trying send data to
    40. 

  40. + the specified address on the given protocol.  The the number of the system
    41. 

  41. + error that cause the problem is given in the message.
    42. 

  42. 

  43. RECVTMO     receive timeout while waiting for data from %1(%2)
    44. 

  44. + An upstream fetch from the specified address timed out.  This may happen for
    45. 

  45. + any number of reasons and is most probably a problem at the remote server
    46. 

  46. + or a problem on the network.  The message will only appear if debug is
    47. 

  47. + enabled.
    48. 

  48. 

  49. UNKORIGIN  unknown origin for ASIO error code %1 (protocol: %2, address %3)
    50. 

  50. + This message should not appear and indicates an internal error if it does.
    51. 

  51. + Please enter a bug report.
    52. 

  52. 

  53. UNKRESULT  unknown result (%1) when IOFetch::stop() was executed for I/O to %2(%3)
    54. 

  54. + The termination method of the resolver's upstream fetch class was called with
    55. 

  55. + an unknown result code (which is given in the message).  This message should
    56. 

  56. + not appear and may indicate an internal error.  Please enter a bug report.
    57.