[erlang-questions] file:sync

[Sean Hinde]

On 8 Mar 2007, at 22:50, Matthew Sackman wrote:

> Hi,
>
> Err, I'm slightly surprised there's been no response to this. Surely
> this has massive implications for the reliability of dets and mnesia,
> amongst other things like disk_log and general file operations on  
> win32.
> Or is win32 a second-class citizen for Erlang?

I think you have answered your own question. If anyone at all used  
Erlang on windows in any sort of production environment then this  
would have been discovered and fixed long ago.

As far as I am aware *no-one* is running anything meaningful in  
erlang under windows.

Sean

>
> On Wed, Mar 07, 2007 at 12:20:08PM +0000, Matthew Sackman wrote:
>> So, for ./erts/emulator/drivers/unix/unix_efile.c
>>
>> int
>> efile_fsync(Efile_error *errInfo, /* Where to return error codes. */
>> 	    int fd)               /* File descriptor for file to sync. */
>> {
>> #ifdef NO_FSYNC
>> #ifdef VXWORKS
>>     return check_error(ioctl(fd, FIOSYNC, 0), errInfo);
>> #else
>>   undefined fsync
>> #endif /* VXWORKS */
>> #else
>>     return check_error(fsync(fd), errInfo);
>> #endif /* NO_FSYNC */
>> }
>>
>> ok - the important line being the last where fsync is actually called
>> which is in glibc unistd.h which is imported. Fine.
>>
>> Then we have for ./erts/emulator/drivers/win32/win_efile.c
>>
>> int
>> efile_fsync(errInfo, fd)
>> Efile_error* errInfo;		/* Where to return error codes. */
>> int fd;				/* File descriptor for file to sync. */
>> {
>>     return 1;
>> }
>
> Matthew
> -- 
> Matthew Sackman
> http://www.wellquite.org/
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions