More cleanup that needs to be done when an interface is removed

[Brian J. Murrell]

OK Ted.

Pursuant to my adventure in making the client dynamically add and remove
interfaces to it's list of active interfaces I found another thing that
needs "undoing" when an interface it removed.  It's "io" object needs to
be destroyed.  Problem is this however:

isc_result_t omapi_io_destroy (omapi_object_t *h, const char *file, int line)
{
	if (h -> type != omapi_type_io_object)
		return ISC_R_INVALIDARG;
	return ISC_R_SUCCESS;
}

omapi_io_destroy () don't do nothing useful.  :-)  Is it supposed to?  I
would think at a minimum the io object needs to be removed from the
omapi_io_states list, however I am sure there is more to it than that,
like cleaning up the inner and outer references and freeing up it's
storage if it's reference count goes to zero.  Or am I right in reading
that the dereferencing functions do that for you?

b.


--
Brian J. Murrell                              InterLinx Support Services, Inc.
North Vancouver, B.C.                                             604 983 UNIX
        Platform and Brand Independent UNIX Support - R3.2 - R4 - BSD