Re: 2.2.10 network "timer" problems with Interbase
On Mon, Aug 23, 1999 at 12:17:00AM +0000, Marcin Owsiany wrote
> a really weird problem:
> I am using Interbase 5.0 SQL server and client on Debian 2.1 with 2.2.10 kernel.
> However there seems to be a bug either in interbase or in kernel.
> For those who are not familiar with SQL servers: an sql server is started
> by inetd after it gets a connection on port 3050 from an sql client.
> The server then accepts querries for any databases and the connection ends
> after the session finishes.
> The problem is that the client freezes when left inactive for some time. At the
> beginning i suspected DNS timeouts, but then made sure the system does not
> try to use any DNS by changing
> order hosts,bind
> in host.conf to
> order hosts
Before you get too involved with analysing network traffic,
check that this isn't simply InterBase working as designed/
I've never used InterBase, but I used to work with an Oracle
application and the Oracle SQL server would sever any idle
connections after some (configurable) amount of time; this
was touted as for security, but I suspect that it was mainly
a way of closing connections for workstations that had crashed/
been turned off/ whatever. Our application had a "Lock" screen
which closed the connection and re-opened it when the user
supplied their password, which people were encouraged to use to
avoid being cut off without notice.
"Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark