Re: nbproc best practices

2016-10-04 Thread Mariusz Gronczewski
On Tue, 04 Oct 2016 11:40:01 +0200, Holger Just wrote: > Hi Mariusz, > > Mariusz Gronczewski wrote: > > we've come to the point when we have to start using nbproc > 1 (mostly > > because going SSL-only in coming months) and as I understand I have > > to bind each process to

Re: nbproc best practices

2016-10-04 Thread Holger Just
Hi Mariusz, Mariusz Gronczewski wrote: > we've come to the point when we have to start using nbproc > 1 (mostly > because going SSL-only in coming months) and as I understand I have > to bind each process to separate admin socket and then repeat every > command for each process, and in case of

Re: nbproc best practices

2016-10-03 Thread Pavlos Parissis
On 03/10/2016 07:13 μμ, Mariusz Gronczewski wrote: > Hi, > > we've come to the point when we have to start using nbproc > 1 (mostly > because going SSL-only in coming months) and as I understand I have > to bind each process to separate admin socket and then repeat every > command for each

nbproc best practices

2016-10-03 Thread Mariusz Gronczewski
Hi, we've come to the point when we have to start using nbproc > 1 (mostly because going SSL-only in coming months) and as I understand I have to bind each process to separate admin socket and then repeat every command for each process, and in case of stats also sum up the counters. Does any of