You could do a rolling restart if you have more then one php-fpm
instance. If you had only one server, i suppose you could still run two
different instances of php-fpm on different Ports or sockets, so you could
do a rolling restart on even one server.
On Dec 17, 2012 10:08 AM, "Ro Achterberg" <jijwilhosting@gmail.com> wrote:
> php-fpm seems to be missing a feature that could be really useful in a
> shared hosting environment like the one I'm currently setting up.
>
> When dynamically creating pools for new domains, the corresponding unix
> socket isn't being created after having issued a SIGUSR2. It seems that
> currently it is impossible to gracefully create a communication socket
> on-the-fly, which means that php-fpm would have to be stopped/restarted.
> This isn't very handy, for obvious reasons.
>
> Any insights into a graceful solution to this problem would be most
> appreciated!
>
instance. If you had only one server, i suppose you could still run two
different instances of php-fpm on different Ports or sockets, so you could
do a rolling restart on even one server.
On Dec 17, 2012 10:08 AM, "Ro Achterberg" <jijwilhosting@gmail.com> wrote:
> php-fpm seems to be missing a feature that could be really useful in a
> shared hosting environment like the one I'm currently setting up.
>
> When dynamically creating pools for new domains, the corresponding unix
> socket isn't being created after having issued a SIGUSR2. It seems that
> currently it is impossible to gracefully create a communication socket
> on-the-fly, which means that php-fpm would have to be stopped/restarted.
> This isn't very handy, for obvious reasons.
>
> Any insights into a graceful solution to this problem would be most
> appreciated!
>