<br><br><div class="gmail_quote">On Wed, Jul 18, 2012 at 9:33 PM, Bharata B Rao <span dir="ltr"><<a href="mailto:bharata.rao@gmail.com" target="_blank">bharata.rao@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
> My question came from a different angle. glfs_fini() will be destroying the<br>
> entire object. You need to get hold of a new object with glfs_new() and do<br>
> glfs_init() on the new object. I see no real reason in providing a<br>
> glfs_fini() api which will result in partial destruction of glfs_t and also<br>
> lets you to glfs_init() on it again. You might as well leave the glfs_t<br>
> as-is and avoid an extra glfs_init() for the second access.<br>
<br>
</div>I am not doing any re-init on the existing glfs object. I do the 2nd<br>
setup (glfs_new etc) from the scratch.<br>
So I am not expecting glfs_fini to do any partial destruction.<br>
<br>
Forget about re-init etc, all I am asking is I have done glfs_new,<br>
glfs_set_volfile_server and glfs_init and I want to undo it. Can you<br>
provide glfs_fini for this ?<br><br></blockquote><div><br></div><div>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]</div>
<div><br></div><div>Avati</div><div><br></div></div>