|author||Rob Landley <email@example.com>||2005-11-04 20:45:54 +0000|
|committer||Rob Landley <firstname.lastname@example.org>||2005-11-04 20:45:54 +0000|
Size I zapped the bb_close() error, might as well make a TODO item.
Diffstat (limited to 'TODO')
1 files changed, 13 insertions, 1 deletions
@@ -34,10 +34,22 @@ man
+ General cleanup.
+bb_close() with fsync()
+ We should have a bb_close() in place of normal close, with a CONFIG_ option
+ to not just check the return value of close() for an error, but fsync().
+ Close can't reliably report anything useful because if write() accepted the
+ data then it either went out or it's in cache or a pipe buffer. Either way,
+ there's no guarantee it'll make it to its final destination before close()
+ gets called, so there's no guarantee that any error will be reported.
+ You need to call fsync() if you care about errors that occur after write(),
+ but that can have a big performance impact. So make it a config option.
Do a SUSv3 audit
Look at the full Single Unix Specification version 3 (available online at