On Wed, Jul 18, 2012 at 9:33 PM, Bharata B Rao
<address@hidden> wrote:
> My question came from a different angle. glfs_fini() will be destroying the
> entire object. You need to get hold of a new object with glfs_new() and do
> glfs_init() on the new object. I see no real reason in providing a
> glfs_fini() api which will result in partial destruction of glfs_t and also
> lets you to glfs_init() on it again. You might as well leave the glfs_t
> as-is and avoid an extra glfs_init() for the second access.
I am not doing any re-init on the existing glfs object. I do the 2nd
setup (glfs_new etc) from the scratch.
So I am not expecting glfs_fini to do any partial destruction.
Forget about re-init etc, all I am asking is I have done glfs_new,
glfs_set_volfile_server and glfs_init and I want to undo it. Can you
provide glfs_fini for this ?
Of course glfs_fini() will be done in a while. But I am concerned now that glfs_init() on a second object is failing. I will look into that first before glfs_fini() [it should only be a resource leak, not result in a hang as you are reporting]
Avati