BIND 10 trac988, created. 8e1c45388cdecec2658bc3d8ba69efd728f9806c [988] also covered the caes where receiving the request fails.

[BIND 10 source code commits]

The branch, trac988 has been created
        at  8e1c45388cdecec2658bc3d8ba69efd728f9806c (commit)

- Log -----------------------------------------------------------------
commit 8e1c45388cdecec2658bc3d8ba69efd728f9806c
Author: JINMEI Tatuya <jinmei at isc.org>
Date:   Fri Jun 15 15:41:07 2012 -0700

    [988] also covered the caes where receiving the request fails.
    
    it's not actually been observed, and even if it continues the loop
    it's probably less harmful.  but it should make more sense to terminate
    the loop and switch to the new session in this case.

commit 9a24a3143e6eb00ca6e242cccef6b76306c96761
Author: JINMEI Tatuya <jinmei at isc.org>
Date:   Fri Jun 15 15:24:15 2012 -0700

    [988] do not continue after recv_fd fails, which would cause infinite loop.
    
    I did some other cleanups:
    - log the failure regardless of the exact error code returned by recv_fd
      (in fact, when it fails it should always be FD_SYSTEM_ERROR in practice).
    - remove the code comment about that.  It talked about rather unusual case
      and could be misleading.  And, now the detailed version of log message
      provides sufficient information.
    - revise the detailed log message so it will explain more likely reason
      for that and clarify what the admin should do.

commit 28603760451a1f515e68fb196ec5f3ad007edbc5
Author: JINMEI Tatuya <jinmei at isc.org>
Date:   Fri Jun 15 14:48:22 2012 -0700

    [988] refactoring: extract while-select loop in a separate method for tests.
    
    no behavior change.

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