tcp_keepidle & tcp_keepintvl - opinions please

From: <Shaun.Racine_at_intier.com>
Date: Tue, 04 Mar 2003 12:00:30 +0000

Hi all,

We have an Ingres database running on several independent servers using
Tru64 v4.0E or v5.1A, all non-clustered. There is an occasional problem
with client side (Win-NT) applications stopping in such a way they don't
close the connection to the DB server (for instance, if power fails to
client PC, app crashes etc).

CA-Ingres support have suggested reducing tcp_keepidle to 300, and
tcp_keepintvl=15. Which I have tested on our development server and work
as required (dbms server disconnects timed out sessions gracefully).

Before I make these changes to our live servers, are there any 'gotchas' to
consider, or unexpected side-effects?

Info: All users connect to their local Unix server over a local area
network or access via a kilostream link, with some occasional dial-in via
Windows RAS connection.

TIA
Shaun Racine
Received on Tue Mar 04 2003 - 12:02:43 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:44 NZDT