Re: exec in CLI vs. mod_php
| From: | Zeev Suraski | Date: | Fri, 30 May 2003 14:38:17 +0000 |
| Subject: | Re: exec in CLI vs. mod_php | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-2090@lists.php.net to get a copy of this message | ||
At 22:44 29/05/2003, Wez Furlong wrote:
Under apache, you inherit all of the apache sockets when the libc forks and execs your script. This causes some problems (there are one or two bug reports about this in the bug db) with processes waiting around on the sockets. It looks like there was some code in the apache SAPI to avoid this problem, but it is currently commented out with an explanation that it is "problematic". I've asked about this problem a few times, but no one seems to notice my questions or have time to reply. So, we know of the problem, we know roughly how to fix it, but no one can explain why we can't fix it :)IIRC, it has to do with resources. For instance, if you close() a socket that's used by a MySQL link, it ended up breaking the link in the parent process. Did you try looking at the history to see whether there was any info in the commit message? Zeev