Subject | Re: [firebird-support] Threat limit classic server 1.5 |
---|---|
Author | Erich Sturm |
Post date | 2008-03-26T07:51:58Z |
Thank you for your help,
xinetd.conf was the solution. My testsystem is an Debian and there you
will not find the attributes "cps" and "instances" in the conf-file. But
if you use SLES you find a limit of 30 instances.
Erich
Philippe Makowski schrieb:
*
xinetd.conf was the solution. My testsystem is an Debian and there you
will not find the attributes "cps" and "instances" in the conf-file. But
if you use SLES you find a limit of 30 instances.
Erich
Philippe Makowski schrieb:
> Erich Sturm [08-03-25 20.30] :*
>
>> Hello,
>>
>> I support a medical software which used firebird 1.5 on linux, mostly
>> SLES 9 or 10. Our DB's partly larger then 2 GB. So we don't switch to
>> the superserver because gbak needs to much time for backup or restore.
>> Now the developer changed/split his programm and with every start of a
>> (windows) client there will be opened two threats (former only one) on
>> the server. In the past I have had no problems with twenty clients or
>> more but now the possibility of logon on database stopped by 14 clients.
>> The next get the message: "DMDef.DB: Connection could not established.
>> Connection rejected by remote interface." In /var/log/messages I
>> couldn't find any hint.
>> I looked a lot in the internet but find not answer if there is any limit
>> of threats on linux or firebird?
>>
>>
> yes check your values in xinetd.conf
> check cps and instances
> cf : http://linuxfocus.org/English/November2000/article175.shtml
>
>
> ------------------------------------
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://www.firebirdsql.org and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Yahoo! Groups Links
>
>
>
>
> __________ NOD32 2971 (20080325) Information __________
>
> Diese E-Mail wurde vom NOD32 antivirus system geprüft
> http://www.nod32.com
>
>
>
>
*