From: Miklos S. <mi...@sz...> - 2005-05-25 06:15:44
|
> I understand. However, this seems inconsistent in the API: if someone > is using hard_remove, the process using the filesystem will get ENOENT > all of a sudden. It seems better to pass the "-" to the filesystem > and let it at least clean up gracefully. release does this already > (so I can already do an ungraceful cleanup), but no other operation > does it. OK, but this will only work for read/write/fsync and not for fstat/fchmod/fchown/ftruncate. The later will still get ENOENT after unlink. Do you think it makes sense to make a subset of the operations work after unlink? If so I'll do it. Release is special only because open/release pairs are always balanced, and the filesystem should be able to rely on that even if using hard_remove. Thanks, Miklos |