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-20130423
           Sensitive:  0             |                   Resolution:
         Sub-Project:  Core          |                 CVSS Scoring:
Estimated Difficulty:  5             |              Defect Severity:  N/A
         Total Hours:  8.08          |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by muks):

 Merged `trac2198_5` branch to `master` in commit
 `4f3d61ec6d64807a8f174c4d028154732c4bad77`:
 {{{
 * 40de1c1 [2198] Remove unnecessary text from API documentation
 * e85c7ea [2198] Fix library paths to add lib/util/threads/ too (contd.)
 * e974876 [2198] Fix library paths to add lib/util/threads/ too (OpenBSD
 test failure)
 * 36e6a75 [2198] Link libb10-threads in log tests
 * e642b05 [2198] Check that the logger locks the LoggerManager mutex
 before calling log4cplus
 * 84bf517 [2198] Add Mutex::tryLock() and non-blocking variant of
 Mutex::Locker
 * f8dc481 [2198] Fix library paths to add lib/util/threads/ too (Mac OS
 test failure)
 * b9d570e [2198] Link -lpthread in libb10-threads target
 * 2caf9ff [2198] Use a mutex from LoggerManager during logging calls
 }}}

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