BIND 10 #2445: suppress initial log
BIND 10 Development
do-not-reply at isc.org
Sun Dec 2 22:37:46 UTC 2012
#2445: suppress initial log
-------------------------------------+-------------------------------------
Reporter: jinmei | Owner:
Type: defect | UnAssigned
Priority: medium | Status:
Component: Boss of BIND | reviewing
Keywords: | Milestone:
Sensitive: 0 | Sprint-20121204
Sub-Project: Core | Resolution:
Estimated Difficulty: 4 | CVSS Scoring:
Total Hours: 0 | Defect Severity: N/A
| Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by jelte):
* owner: jelte => UnAssigned
* status: assigned => reviewing
Comment:
it was doable :)
So here is a version that optionally creates a new specialized logger
appender (instead of the default stdout), during initialization of the
logging system. It stores all logging events until an actual specification
is processed, at which time all stored events are replayed to the now
fully configured logger. Should this for some reason never happen (say, it
can't connect to msgq), everything that is not replayed (i called it
flushed) is dumped to stdout.
It does not use a ring buffer but a simple vector of logging events, and
it is only usable once (after it has been flushed it will refuse to accept
new events).
I've updated the components to enable this, and any output that still goes
to stdout or stderr is because the offending program is writing directly
there, which should be addressed separately. But apart from that, this
should also solve #1898.
--
Ticket URL: <http://bind10.isc.org/ticket/2445#comment:9>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list