Edit report at https://bugs.php.net/bug.php?id=51973&edit=1
ID: 51973
Comment by: rschmidt at key-systems dot net
Reported by: slogster at gmail dot com
Summary: a way to restart single pools, enable/disable
modules per pool
Status: Analyzed
Type: Feature/Change Request
Package: FPM related
PHP Version: 5.3SVN-2010-06-02 (SVN)
Assigned To: fat
Block user comment: N
Private report: N
New Comment:
Hi all,
I am playing with fpm and chroot using unix sockets for shared web hosting.
There
is also a problem with recreating a missing socket file which requires a
complete
restart of fpm.
Any news on this request here?
Regards,
Ralph
Previous Comments:
------------------------------------------------------------------------
[2011-10-21 13:53:38] dbetz at df dot eu
Hello,
a graceful restart would be really nice .... AFTER ondemand feature :-D
Greetings,
Daniel
------------------------------------------------------------------------
[2011-07-22 08:06:29] uros dot gruber at gmail dot com
+1
This could realy be usefull.
------------------------------------------------------------------------
[2011-07-05 08:18:34] daniele dot pignedoli at gmail dot com
+1
Would be great also the possibility to add fpm pools on-the-fly without having
to restart fpm (causing a downtime to all pools)
------------------------------------------------------------------------
[2010-07-22 23:21:21] [email protected]
Hi there.
There is no way to restart a single pool. If you change the conf file, send a
USR2
signal to the FPM process. All pool will be restarted. If you really don't want
to
restart other pools, you can safely send a QUIT signal the each pool processes.
btw, this bugs makes me think about adding a gracefull restart of FPM.
------------------------------------------------------------------------
[2010-06-13 16:04:20] [email protected]
For enabeling extensions you can use the php_admin_value setting for each pool:
php_admin_value[extension] = extension.so
------------------------------------------------------------------------
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
https://bugs.php.net/bug.php?id=51973
--
Edit this bug report at https://bugs.php.net/bug.php?id=51973&edit=1
