Bug #1691: blocking mode sockets override max_execution_time
| From: | marko at iconmedialab dot fi | Date: | Sat, 10 Jul 1999 18:12:21 +0000 |
| Subject: | Bug #1691: blocking mode sockets override max_execution_time | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-8278@lists.php.net to get a copy of this message | ||
From: marko@iconmedialab.fi
Operating system: RedHat Linux 6.0
PHP version: 3.0 Latest CVS (10/07/1999)
PHP Bug Type: Misbehaving function
Bug description: blocking mode sockets override max_execution_time
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.