Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:57350
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.170 as permitted sender)
MIME-Version: 1.0
Date: Fri, 13 Jan 2012 14:13:57 +0100
Message-ID: <CACs9DU68yoZo8iuVm3F+bceH935rv7DSGSf4MkihaD+cj891xA@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary=14dae9340e6529f2c704b668a319
Subject: FD_SETSIZE warning?
From: landeholm@gmail.com (Hannes Landeholm)

--14dae9340e6529f2c704b668a319
Content-Type: text/plain; charset=ISO-8859-1

I'm flooded with this warning when my system is under a high load and uses
a lot of sockets/file descriptors. I get it in stream_select:

"E_WARNING: E_WARNING caught: stream_select(): You MUST recompile PHP with
a larger value of FD_SETSIZE.
It is set to 1024, but you have descriptors numbered at least as high as
1024.
 --enable-fd-setsize=2048 is recommended, but you may want to set it
to equal the maximum number of open files supported by your system,
in order to avoid seeing this error again at a later date."

Why would you even have a limit for this? Having your application suddenly
crash because of some undocumented arbitrary internal PHP limit is a real
punch-in-the-face for people trying to build robust PHP-CGI applications.
Can someone explain to me why I need to be bothered about this?

~Hannes

--14dae9340e6529f2c704b668a319--