Hi Daniele, Thanks for the patch - I will review it asap and if no problem I will upload it on SVN.
Regards, Bogdan Zappasodi Daniele wrote: > Hello Bogdan, > I will provide the new patch as soon as possible. > About your question: I can have scenarios with large groups of users, both > parallel both sequential forking, it depends from the customer's > requirements. > It is not frequent, but I have already received this kind of requests (more > often for sequential forking). > > regards Daniele > > -----Messaggio originale----- > Da: Bogdan-Andrei Iancu [mailto:[EMAIL PROTECTED] > Inviato: lunedì 28 aprile 2008 22.39 > A: Zappasodi Daniele > Cc: [email protected] > Oggetto: Re: [OpenSER-Users] Increase MAX_BRANCHES value? > > > Hi Daniele, > > Thanks for your work - please generate the patch against the latest > trunk version and opens a new patch item on the tracker and assigned it > to me. I will take a look at the patch to see if you did the changes in > all places. > > BTW, off topic, why do you need more than 32 branches? > > Regards, > Bogdan > > > > Zappasodi Daniele wrote: > >> Hello, >> I'm interested in this question too. >> I have tried to modify the tm module and I have found a solution that >> extends the maximum number of branches and it seems to work, but I'm >> still testing it. >> Can anyone, more expert than me on the tm module, give a look to the >> attached file with my patch? >> >> Bye >> Daniele >> >> >> >> >> Hi, >> thanks for your answer... >> I increased the SHM_MEM_SIZE to 64 and left KG_MEM_POOL_SIZE >> 4*1024*1024 . >> Anyway i found that is not possible to raise MAX_BRANCHES to values >> higher than 30 due to >> tm module internal limitation. >> Bye, >> Marcello >> >> ********************************************************************** >> The information in this message is confidential and may be legally >> privileged. It is intended solely for the addressee. Access to this message >> by anyone else is unauthorized. If you are not the intended recipient, any >> disclosure, copying, or distribution of the message, or any action or >> omission taken by you in reliance on it, is prohibited and may be unlawful. >> Please immediately contact the sender if you have received this message >> inerror. >> >> ********************************************************************** >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.openser.org/cgi-bin/mailman/listinfo/users >> >> > > > > ********************************************************************** > The information in this message is confidential and may be legally > privileged. It is intended solely for the addressee. Access to this message > by anyone else is unauthorized. If you are not the intended recipient, any > disclosure, copying, or distribution of the message, or any action or > omission taken by you in reliance on it, is prohibited and may be unlawful. > Please immediately contact the sender if you have received this message > inerror. > > ********************************************************************** _______________________________________________ Users mailing list [email protected] http://lists.openser.org/cgi-bin/mailman/listinfo/users
