Hi, I am using libuv for async file I/O operations. These file operations are mostly on an NFS mount.
So, if the NFS goes down while reading a file, it would hang, (meaning, I dont get the callback until the NFS is back running). (Also, it is the I/O that gets hung, so it looks like libuv thinks that the I/O is in progress, and uv_cancel would not work on these requests). In this scenario, I have implemented a timeout for 30sec, and if this is triggered, I just cleanup my objects (and my application runs forever doing other stuff). But It looks like I need to keep the related "uv_fs_req" objects, because when the NFS comes back, libuv will try to access these objects to make the callback. I wish to know if there is any "cleaner" way of removing the pending callback when NFS goes down ? Thanks and Best Regards, Ramesh -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
