Re: fork() flood in tcp/wait service again

 Yes, and it is more correctly, because if cps
limit reached, then something ugly happened with this service.

 What practical use of this patch ? If service cann't start for
this connection, then chances are it failed and for next (another
unnecessary fork/exec).
Service must be deactivated for a while.
 With this patch fork/exec will be repeated on every
incoming connection. So we must set cps limit again.


Steve G wrote:
> 
> >Present situation (cps workaround) is much better IMHO.
> 
> What is the cps workaround?
> 
> cps when violated calls svc_deactivate which calls
> deactivate.  That function calls close which empties ALL
> pending connections instead of one.
> 
> -Steve Grubb

--
   Dmitry Perfilyev