At 02:35 PM 30/10/2005 -0500, Michael Sinz wrote:
>Jonathan Gilbert wrote:
>[...]
>> Another minor issue is that the Linux man page for write() (section 2)
>> indicates that there exist filesystems where write() doesn't even guarantee
>> that space on the device has been reserved for the device, let alone that
>> the data has been written. If the two file handles don't know about each
>> other, then we also need to fsync() after every write(), and this creates a
>> race condition in the absence of synchronization.
>
>Those two file handles due to symlinks to the same file will actually be
>handled at the VFS/filesystem layer since they will open the same inode.
>Even if the path is different and the name is different, filehandles really
>only care about the inode it is talking to. So even hardlinks will be
>handled correctly. (Softlinks are even more interesting since the VFS layer
>does all of the softlink translation thus the final actual open operation
>runs against the final target file/inode)
This may be the case on a specific implementation, but is it a portable
guarantee? I'm not sure where to check...
Jonathan Gilbert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Oct 30 20:39:38 2005