Your message dated Thu, 23 Aug 2012 11:39:43 +0200 with message-id <CALjhHG8mx5E+1vyEQs-5=jup21CznMK9=jdx3_waiojzsng...@mail.gmail.com> and subject line Re: [php-maint] Bug#605571: Bug#605571: Bug#605571: Please enable pcntl functions has caused the Debian Bug report #605571, regarding libapache2-mod-php5: Please enable pcntl functions to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 605571: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605571 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libapache2-mod-php5 Severity: wishlist I have PHP code that wants to check the return value of pclose() and I need the pcntl_wifexited() and pcntl_wexitstatus() functions to do the work in a clean/portable way. $status = pclose($handle); if (!pcntl_wifexited($status) || pcntl_wexitstatus($status) != 0) { echo "FAIL"; } Unfortunately that function is only available in the -cli variant of PHP5 for a reason that I ignore. You should either build this module in all variants or provide it as a plugin like all other php-mysql/gd/foo packages. Cheers, -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (150, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---Version: php5/5.3.6-12 This was fixed a long time ago, just forgot to close this bug. O. On Mon, May 30, 2011 at 4:25 PM, Ondřej Surý <[email protected]> wrote: > On Mon, May 30, 2011 at 10:54, Thomas Goirand <[email protected]> wrote: >> On 05/30/2011 02:12 PM, sean finney wrote: >>> That leaves us with the basically the same follow-up question as the >>> cgi stuff above, though: do we want to let php code fork/daemonize? >>> >>> I'm not saying we should immediately back this out or anything; we have >>> a while before the next stable release to discuss this and I'm open to >>> the idea that maybe there is some reason we want to allow this. And really, >>> i think you're doing all the heavy lifting with PHP these days Ondrej, so >>> ultimately it's your opinion/decision that will probably matter most :) >>> >>> >>> sean >> >> When it comes to my use case, I'm using SBOX to protect the executions >> of PHP scripts (not the current version in SID, but a re-worked one, >> which I will publish soon), and not PHP FPM. In my case, you can use >> fork if you like, but at the end of the SBOX configured timeout, your >> process (and it's child) will die anyway. So, in my case, having the >> feature to fork is nice, rather than a security issue. I don't think >> that signals, fork, and so on, are there *only* for daemons. Yes, it's >> nice for them, but there are other use cases. >> >> Also, if you believe that this is a security issue, what could be done >> would be to activate the pcntl functions in the Git, then disable them >> by default in php.ini, don't you think? This way, you still leave the >> user a choice. >> >> By the way, are these functions available for the php5-cli binary >> already? I think they are strongly needed in there. >> >> Your thoughts? > > I like the idea of enabling the pcntl, but disabling all functions > from the extension by default. Implemented in 093d34f as static list, > and few minutes later updated it in 093d34f to pull the list of > functions from php_pcntl.h automatically. > > O. > -- > Ondřej Surý <[email protected]> > http://blog.rfc1925.org/ -- Ondřej Surý <[email protected]>
--- End Message ---
