Daniel-Constantin Mierla writes:
> One idea was to add udp_children and sctp_children parameters (or just
> one like socket_children) that will count as they are set and will
> affect next listen, like:
>
> socket_children=2
> listen=127.0.0.1
> socket_children=8
> listen = ...
>
> The other i
On 8/4/11 8:42 PM, Juha Heinanen wrote:
Henning Westerholt writes:
this is the result of the different server design for UDP and TCP. For
TCP
AFAIK one main dispatcher accepts all the connections and then
distribute them
to the workers. For UDP the workers listen directly on the (one) network
Henning Westerholt writes:
> this is the result of the different server design for UDP and TCP. For
> TCP
> AFAIK one main dispatcher accepts all the connections and then
> distribute them
> to the workers. For UDP the workers listen directly on the (one) network
> socket, so there is no dispa
On Thursday 04 August 2011, Juha Heinanen wrote:
> i have 8 children specified in default file and in cfg file i have:
>
> listen=192.98.101.10:5060;
> listen=udp:127.0.0.1:5070;
> listen=udp:127.0.0.1:5070;
> listen=tcp:127.0.0.1:5070;
> listen=udp:127.0.0.1:5080;
> listen=tcp:127.0.0.1:5080;
> l
i have 8 children specified in default file and in cfg file i have:
listen=192.98.101.10:5060;
listen=udp:127.0.0.1:5070;
listen=udp:127.0.0.1:5070;
listen=tcp:127.0.0.1:5070;
listen=udp:127.0.0.1:5080;
listen=tcp:127.0.0.1:5080;
listen=tcp:127.0.0.1:6060;
that results in 8 tcp receiver processes
