BIND 10 #519: msgq socket recv hang
BIND 10 Development
do-not-reply at isc.org
Thu Aug 18 05:33:35 UTC 2011
#519: msgq socket recv hang
-------------------------------------+-------------------------------------
Reporter: jreed | Owner: zhanglikun
Type: | Status: reviewing
defect | Milestone:
Priority: major | Sprint-20110816
Component: | Resolution:
Unclassified | Sensitive: 0
Keywords: | Sub-Project: DNS
Defect Severity: N/A | Estimated Difficulty: 5.0
Feature Depending on Ticket: | Total Hours: 0
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by naokikambe):
* owner: naokikambe => zhanglikun
Comment:
Hello,
I think this problem is basically that msgq cannot handle asynchronous
queuing properly, but I don't know where is wrong exactly. Anyway, the
changes seem to be only for bob and stats, but these almost look OK. There
are some minor points.
- A new command 'getstats' is introduced into bob. Is this for internal
use only? If no, do we need to define it in bob.spec and to document it in
the manpage of stats and in !ChangeLog? Anyway, when I added 'sendstats'
to bob at #521, I documented these.
- I couldn't see any test for the command in bob. Don't we need?
- If !SessionTimeout raised in stats when waiting for answer from bob,
should we just ignore it?
- If bob returns non-zero to stats, wouldn't any message be needed here?
- Actually 'sendstats' isn't needed. Should we remove it?
- Do we need to check that argument which bob returns is dictionary type?
Best
--
Ticket URL: <http://bind10.isc.org/ticket/519#comment:16>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list