> On May 13, 2016, at 5:04 AM, Georg Mischler <schor...@schorsch.com> wrote: > > Not necessarily. It could also mean having been interrupted by a signal > (except on systems with BSD semantics). I think we had a similar discussion > just recently here, though I can't find it anymore…
You’re right; the Linux man page says: > It is not an error if this number is smaller than the number of bytes > requested; this may happen for example because fewer bytes are actually > available right now (maybe because we were close to end-of-file, or because > we are reading from a pipe, or from a terminal), or because > read() was interrupted by a signal. Which means this would be an intermittent bug on Unix systems as well. Arrgh. Randolph _______________________________________________ Radiance-dev mailing list Radiance-dev@radiance-online.org http://www.radiance-online.org/mailman/listinfo/radiance-dev
