On Thu, 2006-11-16 at 23:31 +0000, Aaron Stone wrote: > > What happens in 2.2.0 is somewhat similar to what is described above: a > > child has done a O_NONBLOCK when another does F_GETFL. This way, the > > client socket ends up being non-blocking - which is not what the calls > > to fgets expect.
Possible fix committed to SVN. Let's see if this resolves the issue. Hopefully as simple as re-setting the flags with flags & ~ O_NONBLOCK to be sure that there isn't a nonblocking bit. Aaron
