lkml.org 
[lkml]   [1996]   [Mar]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: imapd and synchronous writes
Date
> What other option do we application developers have?  Until Linux came
> along, directory updates had always been committed before the call
> returned. There are no facilities provided to applications to let
> them specify that a directory update needs to be committed to disk.

Not true. If you have any modern disk controller that re-orders writes
from its internal cache then you potentially lose. There are file systems
other than the Linux one that do async writes and will have the same
properties.

> "Sorry, you're just screwed" is not an acceptable answer.

Thats a reasonable argument.

> "Theodore Ts'o" <tytso@MIT.EDU> writes:
> > Actually, there is, but it's not portable. If you open the directory
> > using open, and then call fsync on the resulting file descriptor, you
> > will forcibly commit the directory change. This is *not* guaranteed to
> > work on all POSIX systems, and indeed it may not work on many. But it
> > will work under Linux.
>
> How is an application, written to compile on a broad range of unix
> systems, to know it has to take this particular set of steps?

Add it to gnu autoconf



\
 
 \ /
  Last update: 2005-03-22 13:36    [W:0.042 / U:2.880 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site