diff options
author | Rob Landley | 2005-11-04 20:45:54 +0000 |
---|---|---|
committer | Rob Landley | 2005-11-04 20:45:54 +0000 |
commit | 7b7c99ca333b832c0d017292436f42efd71589cd (patch) | |
tree | 27373e0accdf8c7a291fc1d4a4356590737bee2a /TODO | |
parent | 3fc4ad1478e1c170d5a939104d5278ac90ca9e6f (diff) | |
download | busybox-7b7c99ca333b832c0d017292436f42efd71589cd.zip busybox-7b7c99ca333b832c0d017292436f42efd71589cd.tar.gz |
Size I zapped the bb_close() error, might as well make a TODO item.
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 14 |
1 files changed, 13 insertions, 1 deletions
@@ -34,10 +34,22 @@ man --- bzip2 Compression-side support. - +--- +init + General cleanup. Architectural issues: +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 "http://www.opengroup.org/onlinepubs/009695399/nfindex.html") and |