Hi,
master process listens to the same port as the pool because of the spawn
dynamic process, you are right. Using epoll, it can know when a new
connexion arrives and then decides wether or not to fork a new process.
Each pool process uses several FD. Once for communicating both way with the
master process, once for logging (if I remember correctly), one for the
socket on the server side and one for the socket for the client. The number
attributated to FD is not supposed to be consistent and can vary as it's
allocated by kernel.
++ Jerome
2013/5/14 Renzo Racioppi <hellforgetm@gmail.com>
> In particular, I noticed that all process of certain pool write at their
> FD 3 when a request for that pool comes. ltrace clearly shows that only one
> process writes an HTML page, but strace instead shows a really confused
> output. I have also noticed that also PHP-FPM master process listens to the
> same port of the pool, I think it does this, on order to know when spawn
> dynamic process.
>
> What I have found about PHP-FPM process interaction on the web, presents a
> too high-level description, mostly oriented to web developers. FPM official
> page describes only module directives. I would like instead to know how
> things are really working.
>
> Regards.
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "highload-php-en" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to highload-php-en+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
---
You received this message because you are subscribed to the Google Groups "highload-php-en" group.
To unsubscribe from this group and stop receiving emails from it, send an email to highload-php-en+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.