Behaviour on 3.0.9:
If a socket is in blocking mode, feof() hangs until
receiving output on the socket, overriding the maximum
execution time defined for the script. If, however,
the socket is in non-blocking mode, everything works ok.

Behaviour on the current CVS (after today's fsock.c patch):
Non-blocking mode behaves just like blocking mode,
and my scripts hang indefinitely if they don't
receive input on their open input sockets, whether
in blocking mode or not.

Desired behaviour:
when max_execution_time passes, script is terminated,
whether or not it is awaiting input from a blocking mode
socket.