On Jan 2, 2007, at 5:00 PM, Sam Lang wrote:

This happened because BMI called BMI_meth_set_info() after BMI_meth_finalize(). I now handle this case. Are there any other calls (other than possibly BMI_meth_method_addr_lookup() and BMI_meth_rev_lookup_unexpected()) that can be called after BMI_meth_finalize()?

<hickup>

We should probably just make sure that nothing gets called after BMI_meth_finalize. Do you know where exactly those calls are being made?

-sam

The call to BMI_meth_set_info() is to free the BMI method addr struct (i.e. the struct that holds the hostname, port, etc). It frees some memory that will not be used again. I was not handling as I should but I am now. I have not come across any other calls after finalize.

On a separate note, I have noticed that when using pvfs2-statfs that the client shuts down before the server sends its last message which is never delivered. MX sees it time out.

Scott
_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers

Reply via email to