BIND 10 #2198: make sure InterprocessSyncLocker is thread safe

[BIND 10 Development]

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

Comment (by muks):

 Replying to [comment:40 vorner]:
 > Looking at the code, it looks sane an mostly OK. Just, around the
 lock()/unlock()/tryLock methods in mutex, the comments say not to use the
 method directly. But the methods are private. I guess the comment is
 useless there.

 These are now removed.

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