BIND 10 #2988: check and report log4cplus rotation issues

[BIND 10 Development]

#2988: check and report log4cplus rotation issues
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:
           Component:  logging       |  Sprint-20130709
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  2             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:6 jreed]:
 > It mostly works but sometimes I have logs out of order, for example:
 > {{{
 > -rw-r--r--  1 root  reed  1049289 Jun 22 23:15 bind10.log.15
 > -rw-r--r--  1 root  reed  1049512 Jun 23 09:48 bind10.log.14
 > -rw-r--r--  1 root  reed  1049053 Jun 23 21:48 bind10.log.12
 > -rw-r--r--  1 root  reed  1049104 Jun 23 22:00 bind10.log.11
 > -rw-r--r--  1 root  reed  1049588 Jun 24 00:00 bind10.log.13
 > -rw-r--r--  1 root  reed  1049514 Jun 24 09:49 bind10.log.10
 > -rw-r--r--  1 root  reed  1049271 Jun 24 12:00 bind10.log.9
 > }}}
 >
 > See the last log entries; bind10.log.13 is in odd order:

 Could it be possible that the offending process uses the
 wrong/unpatched version of liblog4cplus?

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