BIND 10 #2198: make sure InterprocessSyncLocker is thread safe

[BIND 10 Development]

#2198: make sure InterprocessSyncLocker is thread safe
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |  UnAssigned
            Priority:  medium        |                       Status:
           Component:  logging       |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20130402
         Sub-Project:  Core          |                   Resolution:
Estimated Difficulty:  5             |                 CVSS Scoring:
         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


Comment:

 Please review the `trac2198_5` branch. This introduces a mutex inside a
 process to synchronize threads calling log4cplus.

 I have tested that this causes lettuce runs on my local machine to pass,
 whereas it always fails on master.

 But I have also seen at least one intermixed log message with this branch.
 So please review the branch carefully to see if you find anything that may
 cause a race.

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