BIND 10 #1745: adding pid to auth (and resolver) log ID

[BIND 10 Development]

#1745: adding pid to auth (and resolver) log ID
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  jinmei                             |                Status:  reviewing
                       Type:         |             Milestone:
  defect                             |  Sprint-20121204
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  logging                            |  Estimated Difficulty:  2
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => UnAssigned
 * status:  assigned => reviewing


Comment:

 Up for review. Instead of adding the pid to the logger name, the log4cplus
 pattern was updated to include the pid. Here is a snippet of the output
 generated by `features/multi_instance.feature`:
 {{{
 2012-11-26 03:25:01.289 DEBUG [b10-auth.cc/12036] CC_ESTABLISHED
 successfully connected to message queue daemon
 2012-11-26 03:25:01.290 DEBUG [b10-auth.cc/12036] CC_SUBSCRIBE subscribing
 to communication group Auth
 2012-11-26 03:25:01.291 DEBUG [b10-auth.cc/12037] CC_ESTABLISH trying to
 establish connection with message queue daemon at
 /home/muks/bind10/msgq_socket
 2012-11-26 03:25:01.291 DEBUG [b10-auth.cc/12037] CC_ESTABLISHED
 successfully connected to message queue daemon
 }}}

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