This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: How write() works

Hi Tomas,

Thanks for your response.

On 30/11/2010 16:58, tomas@tuxteam.de wrote: 

Yes, it's most definitely (1). The kernel usually decides when commit to
media happens, possibly juggling things to increase throughput. Elevator
and all those things. It wouldn't make sense to put the app to wait for
as long as this happens.
Yeah, this is what I thought. 
See fsync(2) if you want to make sure that things are on disk (well,
there's the cache on the disk drive; it's turtles all the way down ;-)

That's useful - I'd forgotten about fsync(). Thanks.

Marcus.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]