Re: Bug in log.c

a hard limit to reach in normal life - but can still become an issue if 
someone is trying to crash the machine...
for example, opening 2000 concurrent connections to the machine from the 
outside will pass the 1024 barrier without any problem...

Stipe Tolj wrote:

>>a) change gwthread code to use the freed slot ID number instead of
>>incrementing. So we will never have a thread id above 1024 (which is
>>the hard thread limit).
>>b) thing how we can map the thread to the exlusive log file
>>    
>>
>
>to be honest I'd like to pick a), because b) should be pretty fast
>because the logging functions are called a lot on high-load systems,
>so this has to be very fast and array lookups are pretty fast.
>
>Stipe
>
>[email protected]
>-------------------------------------------------------------------
>Wapme Systems AG
>
>Vogelsanger Weg 80
>40470 Düsseldorf
>
>Tel: +49-211-74845-0
>Fax: +49-211-74845-299
>
>E-Mail: [email protected]
>Internet: http://www.wapme-systems.de
>-------------------------------------------------------------------
>wapme.net - wherever you are
>  
>