BIND 10 #2582: Let msgq connect to itself
BIND 10 Development
do-not-reply at isc.org
Tue Jan 15 12:46:30 UTC 2013
#2582: Let msgq connect to itself
-------------------------------------+-------------------------------------
Reporter: vorner | Owner:
Type: task | UnAssigned
Priority: medium | Status:
Component: msgq | reviewing
Keywords: | Milestone:
Sensitive: 0 | Sprint-20130122
Sub-Project: Core | Resolution:
Estimated Difficulty: 7 | CVSS Scoring:
Total Hours: 0 | Defect Severity: N/A
| Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by vorner):
* owner: vorner => UnAssigned
* status: accepted => reviewing
Comment:
Hello
It should be ready for review. There was a small catch, the way I proposed
in
the ticket description would most probably deadlock, so I introduced some
threads to take care of that. They should be safe, there'd be two threads
running in parallel, but the locks would prevent them from doing anything
except for basic read-only operations or manipulation with data not shared
to
the other (the config library in one thread, the poller/kqueue in the
other) at
the same time.
Since some of the things were little bit hard to test, I added a basic
lettuce
test for it.
Proposed changelog:
{{{
[func] vorner
The message queue daemon now appears on the bus. This has two effects, one
is
it obeys logging configuration and logs to the correct place like the rest
of
the modules. The other is it appears in bindctl as module (but it doesn't
have
any commands or configuration yet).
}}}
--
Ticket URL: <http://bind10.isc.org/ticket/2582#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list