Thats exactly the problem. IF the OS was aware of it, then there would be no problem. There is also no setting for timeouts etc when performing blocking operations onto the filesystem. Maybe that is a OS X limitation??
Boris On 14.06.2010, at 17:04, Ken Thomases wrote: > On Jun 14, 2010, at 4:52 AM, Boris Prohaska wrote: > >> i was just wondering, is there any way to determine when for example a >> network cable is plugged off while copying data to a network share? The >> Finder has a pretty long timeout... >> >> Is there a way in the FS API or ANY other way to get notified, when a volume >> isn't available for writing anymore? > > If you just want to know when a volume disappears (is unmounted), NSWorkspace > provides notifications for that. But I don't think that will address the > issue you describe. > > The problem is that the volume hasn't disappeared, it's just incommunicado as > far as the OS is concerned. If it had disappeared in a way that the OS was > aware of, then there would be no way for something to be stuck writing to it > (or to begin writing to it, etc.). That is, there would be no paths to it > for opening new file descriptors and all existing file descriptors would > return errors on access. > > -Ken _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
