BIND 10 #1321: Allow sending notify manually
BIND 10 Development
do-not-reply at isc.org
Fri Mar 9 17:39:34 UTC 2012
#1321: Allow sending notify manually
-------------------------------------+-------------------------------------
Reporter: | Owner: UnAssigned
vorner | Status: reviewing
Type: | Milestone:
enhancement | Sprint-20120320
Priority: | Resolution:
medium | Sensitive: 0
Component: | Sub-Project: DNS
xfrout | Estimated Difficulty: 4
Keywords: | Total Hours: 2
Defect Severity: N/A |
Feature Depending on Ticket: |
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by jelte):
* owner: jelte => UnAssigned
* status: assigned => reviewing
* totalhours: 0 => 2
Comment:
Ok, initially i was tempted to sneak it a bit more improvements, but those
would be non-trivial and worthy of a separate ticket (mailed -dev about
it: https://lists.isc.org/pipermail/bind10-dev/2012-March/003200.html)
So right now, I've changed the internal command name to 'notify' instead
of 'zone_new_data_ready' and added it to the spec file for commands, so it
shows up in bindctl.
notify_out's send_notify() call now also returns True or False, depending
on whether the zone was found (so that bindctl ends up reporting an error
if not).
--
Ticket URL: <http://bind10.isc.org/ticket/1321#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list