Querying file information and concurrent file access
Posted Apr 29, 2011 16:01 UTC (Fri) by dark
In reply to: Querying file information and concurrent file access
Parent article: The return of SEEK_HOLE
I think it makes sense. It's not really different from a read() that might return data that's already obsolete because another process is writing there. This can be fixed with locks or other techniques (such as tar's habit of displaying a warning if the file changed), and it's up to you to use them if you want to.
to post comments)