exported / execap

Automatically exported from code.google.com/p/execap
GNU General Public License v3.0
0 stars 0 forks source link

Need to check for failed write() calls #25

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
If the disk is full (or for various other reason) write() can fail.  Right now 
that can happen silently.  Error checking needs to be added so that errors like 
ENOSPACE can be reported.

Original issue reported on code.google.com by bmenr...@ucsd.edu on 11 May 2011 at 11:16