parent
c11e02df7c
commit
8679482c72
|
@ -374,7 +374,7 @@ eet_flush2(Eet_File *ef)
|
||||||
if (!fp)
|
if (!fp)
|
||||||
return EET_ERROR_NOT_WRITABLE;
|
return EET_ERROR_NOT_WRITABLE;
|
||||||
|
|
||||||
fcntl(fileno(fp), F_SETFD, FD_CLOEXEC);
|
fcntl(fd, F_SETFD, FD_CLOEXEC);
|
||||||
}
|
}
|
||||||
else
|
else
|
||||||
return EET_ERROR_NOT_WRITABLE;
|
return EET_ERROR_NOT_WRITABLE;
|
||||||
|
@ -507,14 +507,6 @@ eet_flush2(Eet_File *ef)
|
||||||
|
|
||||||
/* flush all write to the file. */
|
/* flush all write to the file. */
|
||||||
fflush(fp);
|
fflush(fp);
|
||||||
// this is going to really cause trouble. if ANYTHING this needs to go into a
|
|
||||||
// thread spawned off - but even then...
|
|
||||||
// in this case... ext4 is "wrong". (yes we can jump up and down and point posix
|
|
||||||
// manual pages at eachother, but ext4 broke behavior that has been in place
|
|
||||||
// for decades and that 1000's of apps rely on daily - that is that one operation
|
|
||||||
// to disk is committed to disk BEFORE following operations, so the fs retains
|
|
||||||
// a consistent state
|
|
||||||
// fsync(fileno(fp));
|
|
||||||
|
|
||||||
/* append signature if required */
|
/* append signature if required */
|
||||||
if (ef->key)
|
if (ef->key)
|
||||||
|
|
Loading…
Reference in New Issue