|
Hello,
On Tue, 6 Dec 2005, Roberto Nibali wrote:
> This dead code has been there for ages, without any notion of why it was
> kept there. What are the use cases for per-proto and per-app?
>
> per-proto: TCP, UDP, ICMP, IP?
> per-app : ftp
Yes, even per-service: 5 seconds for DNS, 10 for RADIUS,
120 seconds for ISAKMP. It is possible to attach different timeout
table with different per-state timeouts for different app or service.
> Is this what you mean? And if so, is it simply a matter of splitting up
> the reinstated code into those per-proto zones?
May be, i don't remember, may be secure_tcp does not use them
anymore.
> Please resend them again if you have time, since I can't find them. Also
> note, that to me a pragmatic approach already helps, no over-engineering
> needs to be done. The only real timeouts you ever need to set in 99.999%
> of the cases are TCP related.
I'll summarize later today. Yes, one can live with global values
for all virtual servers, in other cases it can be useful to have different
values just to save memory.
Regards
--
Julian Anastasov <ja@xxxxxx>
|
