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):

 Replying to [comment:46 jreed]:
 > e642b05  duplicates noinst_SCRIPTS  = console_test.sh  and following
 lines.

 Thank you for catching this. I've fixed it in `master` now.

 > Also a Changelog entry is missing for this.

 I don't think a `ChangeLog` is required as it's got no changes to affect a
 user's view (neither bugfix in parsing something, nor some new
 functionality change). It just grabs another lock before logging. But if
 you feel strongly that it requires a `ChangeLog` entry, we'll add one.

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