Re: Question about socket ext. file descriptors
| From: | Zeev Suraski | Date: | Thu, 29 Mar 2001 13:59:19 +0000 |
| Subject: | Re: Question about socket ext. file descriptors | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-50223@lists.php.net to get a copy of this message | ||
ext/sockets does indeed appear to be broken; It doesn't obey the standard PHP return value rules at all (errors are negative numbers instead of false, resource are passed back as-is instead of as resources).
I was actually looking at the other socket functions, fsockopen() and friends. They're ok.
Zeev
At 15:52 29/3/2001, Andi Gutmans wrote:
Well we were talking about the ext/socket extension and all functions there which create file descriptors are leaking. It's not an exception. Check open_listen_sock() and accept_connect(). You were probably looking at the fd set functions which are just emalloc()'ed memory. The happen to use resources but even if they hadn't it would be a leak which the Zend memory manager would clean up. The file descriptors is the real problem. Andi-- Zeev Suraski <zeev@zend.com> CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/