Comment 3 for bug 479451

Personally I am still wary on 5.3.x + fpm.

I will say that it is expected behavior in the logfile to show the child being send SIGCHLD as that occurs when it has hit max_requests and is recycling the PHP process.

This is what I show when a child is being restarted (5.2.11 w/ patch)

Jan 07 11:46:44.247761 [NOTICE] fpm_got_signal(), line 48: received SIGCHLD
Jan 07 11:46:44.247843 [NOTICE] fpm_children_bury(), line 215: child 18159 (pool default) exited with code 0 after 1447.637682 seconds from start
Jan 07 11:46:44.248313 [NOTICE] fpm_children_make(), line 352: child 20218 (pool default) started