[967] in linux-net channel archive
Re: heavily-accessed site w/ random hangs on specific port... suggestions? (fwd)
daemon@ATHENA.MIT.EDU (Willem van der Oord)
Wed Aug 23 13:10:10 1995
Date: Tue, 22 Aug 1995 12:52:14 -1000 (HST)
From: Willem van der Oord <willem@hpa.edu>
To: Michael Brennen <mbrennen@puddytat.intecom.com>
cc: linux-net@vger.rutgers.edu, Eric Ost <emo@cica.cica.indiana.edu>
In-Reply-To: <Pine.LNX.3.91.950821095716.9981B-100000@puddytat.intecom.com>
> ---------- Forwarded message ----------
> Date: Sat, 19 Aug 1995 20:54:24 -0500
> From: Eric Ost <emo@cica.cica.indiana.edu>
> To: wu-ftpd@wugate.wustl.edu
> Subject: heavily-accessed site w/ random hangs on specific port... suggestions?
>
[...]
> We have been experiencing strangeness whereby the system "burps" for a,
> sometimes extended, period of time, and connections to port 21 are not
> possible -- they just timeout. However, we configured an ftp service
> for port 1111 and have discovered that during a "burp" on port 21,
> connections to wu-ftpd running on port 1111 are just fine. Telnet (login)
> to the machine also works speedily. Random delays have occurred with as low
> as 90 and as high as 190 simultaneous connections to port 21; the more
> connections, the more likelihood of a delay...
I've seen this exact problem on a MUD running on port 5000 with
approximately 100-130 people connected. It's oddly unpredictable -- we'd
go for a month or so without any problems, but then for a week, this
problem would crop up constantly. Then it would mysteriously disappear
again. All this occurs without any change in configuration. Killing and
restarting the mud process would temporarily alleviate the problem,
sometimes only for a few minutes.
> In all of the above instances, xinetd is playing the role of mediator
> between the incoming request and invoking the proper server.
Since it is a MUD, there is only one process involved in dealing with
the connections.
-Willem
