ID: 38915 Comment by: gabe-php at mudbugmedia dot com Reported By: dimmoborgir at gmail dot com Status: Open Bug Type: Feature/Change Request Operating System: UNIX PHP Version: 5.2.2, 4.4.7 New Comment:
I'm also running into a problem where, because my Apache is hosting 500+ vhosts, gobbling up 1000+ descriptors for logs. All this gets passed to any program it executes, causing problems with processes with a 1024 limit compiled in. Apache might be able to deal with having that many descriptors open, but we shouldn't assume anything PHP execs should. Previous Comments: ------------------------------------------------------------------------ [2007-12-04 19:14:45] [EMAIL PROTECTED] I think that's exactly what FD_CLOEXEC does. ------------------------------------------------------------------------ [2007-12-04 18:43:04] crescentfreshpot at yahoo dot com Just to add to the dialog, Apache 1.x seems to have tried to address the issue of leaked FDs itself. http://www.apache.org/dist/httpd/CHANGES_1.3 says: Changes with Apache 1.3.28 *) Certain 3rd party modules would bypass the Apache API and not invoke ap_cleanup_for_exec() before creating sub-processes. To such a child process, Apache's file descriptors (lock fd's, log files, sockets) were accessible, allowing them direct access to Apache log file etc. Where the OS allows, we now add proactive close functions to prevent these file descriptors from leaking to the child processes. As far as I understand the above, apache thinks it can know when [mod_]php does a system-level popen() and cleanup the parent FDs before exec(). Is that actually possible? ------------------------------------------------------------------------ [2007-11-29 20:33:42] odeta at hard dot lt Any news? mail() function is suffering from the same problem, and exim is using Apache port then.. ------------------------------------------------------------------------ [2007-11-25 19:57:51] olafvdspek at gmail dot com Can't you use FastCGI and avoid issues like these completely? ------------------------------------------------------------------------ [2007-10-07 09:33:33] Cruz at guerillamail dot com Ran into the same problem. I'm appalled that a bug this big isn't fixed more than a year after it was reported. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/38915 -- Edit this bug report at http://bugs.php.net/?id=38915&edit=1
