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      |
-------------------------------------+-------------------------------------

Comment (by muks):

 If we are to pick up the `tryLock()` bits of `Mutex` and `Mutex::Locker`
 from the other branches, we can test if the `Mutex` in `LoggerManager` is
 locked at least, before log4cplus is used. But I'm not sure if we should
 test it.. let me know in the review.

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