BIND 10 #2198: make sure InterprocessSyncLocker is thread safe

[BIND 10 Development]

#2198: make sure InterprocessSyncLocker is thread safe
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  jinmei                             |                Status:  reviewing
                       Type:         |             Milestone:
  defect                             |  Sprint-20121106
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  Core
  logging                            |  Estimated Difficulty:  5
                   Keywords:         |           Total Hours:  3.85
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => UnAssigned
 * status:  assigned => reviewing


Comment:

 This has been implemented in the `trac2198_4` branch.

 I have not added a test such as the interprocess one in
 `logger_lock_test.cc` + `logger_lock_test.sh.in` as it involves adding
 more API for passing mock objects and such. It wouldn't test logging calls
 from 2 threads deterministically to catch a race. The `Mutex` and
 `Mutex::Locker` are already tested in `util/threads/tests/`.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2198#comment:32>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development