Thanks a lot !
> I just have to say the php_defines option saved me some hassle, I was
> able to set heavy error reporting on a single FastCGI pool and not
> across everything. So nice. So so nice!
>
> I've already migrated everything I do to use php-fpm. It's awesome. I
> cannot praise you enough, Andrei.
>
> Quick question: when I do php-fpm reload or php-fpm restart, does it
> physically kill the existing engines and someone could get a 502 bad
> gateway during that little bit of time, or does it somehow do it in a
> graceful fashion? It seems to restart so quick (and reload even
> quicker) that it doesn't even trip up my healthchecks so far... I'm
> wondering if it's doing it gracefully on purpose or it just works
> really fast.
"reload" does send SIGUSR2 to master process.
When SIGUSR2 is sent to master process it does gracefull reload and would
never cause requests to be aborted in the middle, unless some workers have
been unable to react on signals within process_control_timeout.
"restart" is composed from "stop" and "start", which may cause aborted
requests to happen some times.
--
Andrei Nigmatulin
GPG PUB KEY 6449830D
Now I lay me down to sleep(3)
Pray the OS my core to keep
If I die before I wake
Pray the Disk my core to take
Yes, this to be added into next release.