See http://www.redhat.com/support/errata/RHSA-2001-006.html.  RedHat issued
an errata note saying the problem solved with the new RPMS was:

RH> 
RH> 
RH>  1. Topic:
RH> 
RH>  The inetd server as shipped with Red Hat Linux 6.2 fails to close sockets
RH>  for internal services properly. 
RH> 
RH>  2. Problem description:
RH> 
RH>  The inetd server as shipped with Red Hat Linux 6.2 fails to close sockets
RH>  for internal service properly. This could make services stop working when
RH>  the system had leaked sufficient resources.
RH> 
RH>  Note that all of these services are turned off in the default configuration. 
RH> 
RH>  3. Bug IDs fixed: (see bugzilla for more information) 
RH> 
RH>  16729 - inetd does not close connection when daytime service is called
RH>  15908 - Misspelled variable in inetd start script
RH> 
RH>  4. Relevant releases/architectures:
RH> 
RH>  Red Hat Linux 6.2 - alpha, i386, sparc
<SNIP>

Austad, Jay wrote:
> 
> It's running redhat 6.2, and the connections are all to rmserver
> (RealServer), which runs as it's own daemon, not through inetd.  Maybe it's
> a problem with rmserver?  I have 2 clones of this box though, and neither of
> those have any problems, and they all get the same amount of traffic.
> 
> Jay
> 
> > -----Original Message-----
> > From: Nate Carlson [mailto:natecars at real-time.com]
> > Sent: Tuesday, January 30, 2001 5:18 PM
> > To: 'tclug-list at mn-linux.org'
> > Subject: Re: [TCLUG] tcp connections not closing properly
> > 
> > 
> > On Tue, 30 Jan 2001, Austad, Jay wrote:
> > > I have a box that is not properly closing out it's tcp 
> > connections.  If I do
> > > a netstat --inet, it comes up with over 1700 connections in 
> > the state CLOSE.
> > > lsof shows all of these using up my file handles, and I am 
> > having trouble
> > > starting new processes on the box so I have to reboot it.
> > >
> > > Does anyone know how I can fix this?  I have 2 machines 
> > which are identical
> > > to this one and they don't have any problems.
> > 
> > What kernel version, and what type of TCP connections?
> > 

Hope this helps, 

-S