Hi Conrad,
I agree that under normal circumstances, the intermediate process shouldn't
be abnormally terminated. However, I was interested in understanding the
behaviour in case of such an occurrence (though unlikely). The only "fix"
I can imagine is reaping of such orphan processes. Thanks for t
Hi,
On 02/27/2016 02:23 AM, BR Kumar wrote:
> Hi Conrad,
>
> Thanks for responding. Regarding point (2), I'm not sure the last level of
> child processes are awaiting connection closure and would exit afterwards.
> In my test, netstat showed no connection against the haproxy port. Yet, the
> orph
Hi Conrad,
Thanks for responding. Regarding point (2), I'm not sure the last level of
child processes are awaiting connection closure and would exit afterwards.
In my test, netstat showed no connection against the haproxy port. Yet, the
orphaned child process continued indefinitely. To reiterate,
Hi Bharat,
On 02/24/2016 03:04 AM, BR Kumar wrote:
> Couple of questions related to the systemd wrapper:
>
> 1) I noticed that it spawns a 2 level hierarchy of haproxy processes
> instead of a single child process. Can someone help understand why?
It's a little complex, but I can try:
It is pro
Couple of questions related to the systemd wrapper:
1) I noticed that it spawns a 2 level hierarchy of haproxy processes
instead of a single child process. Can someone help understand why?
2) The problem arises when the intermediate haproxy process dies for any
reason and the child process is ado
5 matches
Mail list logo
