BIND 10 #2198: make sure InterprocessSyncLocker is thread safe

[BIND 10 Development]

#2198: make sure InterprocessSyncLocker is thread safe
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  muks
  jinmei                             |                Status:  assigned
                       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 jinmei):

 I suggest we first discuss whether we really want to solve this issue
 ourselves.

 And, if we do, I suggest a much simplified approach: have
 `LoaggerManager` maintain a single global mutex, and we use it
 `LoggerImpl::outputRaw()`.  `LoaggerManager` is the most reliable
 singleton in the logging framework (relying on how applications
 perform logging initialization), so it's probably the best to
 implement it on top it, rather than introducing yet another point of
 singleton.

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