25 Jul
2005
25 Jul
'05
1:08 p.m.
Clemens Kirchgatterer clemens@1541.org wrote:
Martin Cap macap20001@compuserve.de wrote:
Today I tried to set O_NONBLOCK to the open()-calls (the code does a
"do{ r = read(...); }while(r!=-1 && r != EINTR);" at stream.c:271
shouldn't it be: while(r!=-1 && errno != EINTR); ?
when i think about it, i'd rather do { r = read(...); } while (r >= 0 || ((r < 0) && (errno == EINTR)));
b.t.w. doesn't that eat cpu like crazy when O_NONBLOCK is set?
clemens