Content-Transfer-Encoding: binary
Content-Disposition: inline
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
X-RT-Interface: Web
In-Reply-To: <rt-4.4.1-18210-1498437032-1793.28194-0-0@isc.org>
X-RT-Original-Encoding: utf-8
Message-ID: <rt-4.4.1-18210-1498437848-411.28194-0-0@isc.org>
References: <20120229171118.5579f766@shane-desktop>
 <RT-Ticket-28194@isc.org>
 <rt-4.4.1-18210-1498437032-1793.28194-0-0@isc.org>
X-Mailer: MIME-tools 5.508 (Entity 5.508)
RT-Send-CC:
Content-Length: 366

On Sun Jun 25 14:30:32 2017, marka wrote:
> I don't see any test cases for this error handling.

Additionally there is a case for continuing to fail in
non-iteractive mode.  We may want to add a interactive
mode flag to facilite testing.  We may also want to add
a "fail on error" flag (c.f. "sh -e")  so that errors in programs
feeding nsupdate are easily detected.