Hi Tim,

in Windows, this is called FlushFileBuffers, I guess:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa364439%28v=vs.85%29.aspx

MSDN also suggests to use unbuffered I/O instead of calling such a flush
function too often. What are our options to control buffered vs. unbuffered
from Squeak land?

https://support.microsoft.com/en-us/kb/99794
https://msdn.microsoft.com/en-us/library/windows/desktop/cc644950%28v=vs.85%29.aspx

On what media is the data stored? I think that you cannot be 100% sure to
have all data written after some function call returns because some details
are out of reach for user applications. Think of some USB driver that needs
just two more cycles to finish writing... I am no expert there but it seems
tricky to find the correct point in time to turn the power off. Regular OS
shutdown seems more appropriate...

Best,
Marcel



--
View this message in context: http://forum.world.st/Adding-fsync-call-to-the-primitiveFileFlush-prim-tp4896538p4896545.html
Sent from the Squeak - Dev mailing list archive at Nabble.com.