--- In [email protected], "spudgun0" <[EMAIL PROTECTED]> wrote: > > So, it seems, there's no way to sidestep the buffer > "parking" of the data while writing on disk ... > > I made some test this morning and I realized that my > problem could be in the opening of the file, not in the > writing. I use : > _open (file , _O_CREAT | _O_BINARY | _O_RDWR, > _S_IREAD | _S_IWRITE)) > to open my remote file, and it always succeeds : so I > made the test by just opening and closing the file, > expecting an empty file to be created. > Instead, no file was created at all. <snip>
That sounds understandable to me: I could imagine that after having opened the file in read/write mode the OS is waiting for some initial operation in order to find out what to do next. It could be that you want to write something, it could be that you want to read from a file assuming it exists. So I also can imagine that the OS doesn't generate the file before any such writing operation is actually performed. And actually this makes sense: why should a file be created if there's nothing written to it? I don't say it's correct behaviour; it is just my interpretation of what you describe, so I may as well be completely wrong. It's just an idea that I have. Regards, Nico
