BIND 10 #2900: Investigate and fix mixed and missing log messages
BIND 10 Development
do-not-reply at isc.org
Wed Jun 5 03:38:53 UTC 2013
#2900: Investigate and fix mixed and missing log messages
-------------------------------------+-------------------------------------
Reporter: muks | Owner:
Type: defect | Status: new
Priority: medium | Milestone: Next-
Component: logging | Sprint-Proposed
Keywords: | Resolution:
Sensitive: 0 | CVSS Scoring:
Sub-Project: DNS | Defect Severity: N/A
Estimated Difficulty: 10 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Comment (by jinmei):
I suggest trying to reproduce the issue in a simpler scenario, like
writing a simple multi-process Python program dumping logs and running
it multiple times. We know this happens on macmini.lab.isc.org, so
if we are lucky we should be able to reproduce it on that machine.
And I propose we won't spend too much time for this phase: if we can
reproduce it and can easily identify and fix the cause, do it; if we
can reproduce it but can't easily identify and/or fix the cause, stop
at that point and defer it to a separate ticket; if we can't even
easily reproduce it, stop at that point and keep this ticket open.
This shouldn't be that big as a 10-point task, so I suggest
re-estimating it. Then we can at least make some progress without
worry about too much space from the available points.
--
Ticket URL: <http://bind10.isc.org/ticket/2900#comment:5>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list