So it seems I won't be able to get the behavior I need from uwsgi directly if I understand what you're saying.
Thanks you anyway for all your answers! You refreshed my knowledge about sockets. On Mon, Aug 25, 2014 at 9:36 PM, Roberto De Ioris <[email protected]> wrote: > > > :'( > > > > tcp ESTAB 0 22 127.0.0.1:49107 > > 127.0.0.1:9090 > > users:(("telnet",7844,3)) > > tcp ESTAB 0 0 127.0.0.1:49102 > > 127.0.0.1:9090 > > users:(("telnet",7820,3)) > > tcp ESTAB 0 0 127.0.0.1:49105 > > 127.0.0.1:9090 > > users:(("telnet",7834,3)) > > tcp ESTAB 0 22 127.0.0.1:49113 > > 127.0.0.1:9090 > > users:(("telnet",7884,3)) > > tcp ESTAB 0 0 127.0.0.1:49106 > > 127.0.0.1:9090 > > users:(("telnet",7839,3)) > > tcp ESTAB 0 22 127.0.0.1:49120 > > 127.0.0.1:9090 > > users:(("telnet",7927,3)) > > tcp ESTAB 0 22 127.0.0.1:49118 > > 127.0.0.1:9090 > > users:(("telnet",7913,3)) > > tcp ESTAB 0 22 127.0.0.1:49116 > > 127.0.0.1:9090 > > users:(("telnet",7903,3)) > > tcp ESTAB 0 22 127.0.0.1:49112 > > 127.0.0.1:9090 > > users:(("telnet",7879,3)) > > tcp ESTAB 0 22 127.0.0.1:49111 > > 127.0.0.1:9090 > > users:(("telnet",7870,3)) > > tcp ESTAB 0 22 127.0.0.1:49115 > > 127.0.0.1:9090 > > users:(("telnet",7894,3)) > > tcp ESTAB 0 22 127.0.0.1:49110 > > 127.0.0.1:9090 > > users:(("telnet",7865,3)) > > tcp ESTAB 0 22 127.0.0.1:49119 > > 127.0.0.1:9090 > > users:(("telnet",7918,3)) > > tcp ESTAB 0 22 127.0.0.1:49122 > > 127.0.0.1:9090 > > users:(("telnet",7937,3)) > > tcp ESTAB 0 22 127.0.0.1:49109 > > 127.0.0.1:9090 > > users:(("telnet",7860,3)) > > tcp ESTAB 0 22 127.0.0.1:49117 > > 127.0.0.1:9090 > > users:(("telnet",7908,3)) > > tcp ESTAB 0 22 127.0.0.1:49121 > > 127.0.0.1:9090 > > users:(("telnet",7932,3)) > > tcp ESTAB 0 0 127.0.0.1:49104 > > 127.0.0.1:9090 > > users:(("telnet",7825,3)) > > tcp ESTAB 0 22 127.0.0.1:49114 > > 127.0.0.1:9090 > > users:(("telnet",7889,3)) > > tcp ESTAB 0 22 127.0.0.1:49108 > > 127.0.0.1:9090 > > users:(("telnet",7851,3)) > > > > > > I realized now that you are checking netstat for checking accept()'ed > connection, but ESTABLISHED in modern kernels (at least on Linux and BSDs) > does not mean a process has called accept(). > > Syncookies, max_syn_backlog, the minimal queue length. all changes the > "old" behaviour (in the name of security, first of all) > > The client behaviour (telnet, curl...) is getting connect() in write-ready > state up to the amount of the listen queue (minimal 8 or 16 on Linux), > after this limit the connect() will block until the timeout. But at kernel > level, lot more connections can be in ESTABLISHED state. > > You can play with your kernel tcp tunings, but just for fun :) > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > -- Francois
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
