|Subject||Re: 1.5.1 CS for Linux with xinetd|
--- In firstname.lastname@example.org, "Steffen Heil" <lists@s...>
> Hirestart the
> > After a while my buggy application managed to get xinetd to
> gds_db service for too many open connections.windows.
> > when xinetd allows client connections again, ALL of the previous
> connections remain open on the server..
> > I would expect the existing connetions to get dropped/killed when this
> You seem to see xinetd as some kind of service manager like ssc for
> Thats not true. xinetd is a process launcher.matching
> When a tcp connection to a port is established, xinetd lauches the
> application.will not
> Thats it. The application has nothing more to do with xinetd.
> As classic server handles each connection in a separate process, it
> disconnect old connections when restarting single ones. Old connectionswhich
> without clients will time out and will then be closed.
> However, you can propably archieve what you want using super server,
> is anyway more resourcesaving than classic server when used with manycertain
> > I can't remember if Firebird automatically cleans these up after a
> period of inactivity.any more
> Not, if the client is still alive, but if the client is down and the tcp
> connection times out, there is nothing to do for the server process
> and it will terminate.Thanks Steffen.