Re: refused connections........

Doug Paul (dbp@pluto.dragonsys.com)
Sun, 25 Feb 1996 10:37:10 -0500 (EST)

>
> running kernel 1.3.68
>
> after a short period of time, inetd will start refusing all connections
> untill I kill -HUP it. (it's done this with .60, .62, .64, not sure
> about .67, I only ran it for about 2 minutes)

We have experienced a more limited version of this: inetd will occasionally
start refusing connections on port 80 (very heavily used) while still
allowing connections on other ports. No error messages. Telnet to port 80
will (as I remember) give a connection refused error message. Sometimes
inetd will recover spontaneously in the next hour or so, otherwise a
kill -HUP fixes it. Happens for both 1.2.13 and 1.3.57. (Haven't
tried other kernels on this machine--too many people depend it to reboot
it very often.)

We have a wide range of OSes and browsers connecting to this machine.
Problem might be TCP/IP related or inetd.

Context: Slackware 2.2,
strings inetd => $Id: inetd.c,v 1.1 1994/05/23 09:04:44 rzsfl Exp rzsfl $

Doug
dbp@pluto.dragonsys.com