Date: Tue, 24 Feb 1998 01:52:31 -0800 (PST)
From: tooleym@douglas.bc.ca
To: Nathan Gelbard <gelbard@ENGR.ORST.EDU>
Subject: Re: inetd services looping?

>         2) For the longest time, I was getting these errors in /var/log/messages
> from tftp: Feb 23 23:40:45 3jane inetd[219]: tftp/udp server failing (looping),
> service terminated 
> I wasnt even able to tftp from any box. Now it works for some unknown reason.

Well I know what server failing due to looping service is.. I encountered
it a long time ago when busy using AmiTCP 3.0b2 -- they have hardcoded
there a shitty little puny "requests per second" allowed, and so do we.

I'm not sure if it has been built into an option or not recently, however
I do know this: The way I fixed it was to get the system sources,
including inetd.c , etc, and recompile using a higher "requests per
second"  number. This temporarily solved my problem. It is triggered when
the number of incoming requests exceeds the precompiled static value and
inetd thinks you are being flooded. It's kind of a security "feature".

Anyhow, you can fix it by quickly editing the inetd source #define's and
recompiling, reinstalling inetd. It's very quick an painless to do this.
Trust me. I've done it seven times now. :)

Marc Tooley
tooleym@douglas.bc.ca

     _/_/_/_/  _/    _/  _/_/_/      _/_/      _/_/_/
    _/        _/    _/  _/    _/  _/    _/  _/     
   _/_/_/_/  _/    _/  _/    _/  _/    _/  _/   
        _/  _/    _/  _/    _/  _/    _/  _/    _/_/
 _/_/_/_/    _/_/    _/_/_/      _/_/      _/_/_/
^^ neat huh? looks better on a black background, white foreground. xterm
is cool!