[4075] in linux-net channel archive
Re: shell/tcp server failling(looping)
daemon@ATHENA.MIT.EDU (Rob McKee)
Sat Aug 17 07:14:03 1996
Date: Sat, 17 Aug 1996 03:21:35 -0700 (PDT)
From: Rob McKee <Imcom@imcom.com>
To: Alessandro Suardi <asuardi@uninetcom.it>
cc: linux-net@vger.rutgers.edu, linux-kernel@vger.rutgers.edu
In-Reply-To: <32152990.76CB9A92@uninetcom.it>
I believe it does.. reading news via nntp and using the movement key to
fly by spamming definately triggers it. I have to killall -15 inetd and
restartit.
--
# Rob McKee ImCom.Com 207.33.73.2
# SysAdmin 1630 N. Main St. Suite #444
# Imagine Communications Walnut Creek, CA 94596-4609
#
# (510) 939-1691 BBS (510) 939-1684 Voice
# The best defense is not to have a hay seed for a president
On Sat, 17 Aug 1996, Alessandro Suardi wrote:
> Klaus Lichtenwalder wrote:
> >
> > Hi,
> > I have an application that for simplicity backs up new files from a file
> > server via rsh. Things thingy stops after a few rsh calls to the remote
> > Linux machine. The following message can be found in syslog:
> >
> > Aug 16 17:53:59 gaston inetd[73]: shell/tcp server failing (looping),
> > service terminated
>
> [snip]
>
> > Here's my test-script:
> >
> > while :; do rsh <remote machine name here> pwd; done
> >
> > Cheers,
> > Klaus
>
> SunOS's inetd protected itself from runaway TCP clients bombing it
> with connect requests by declaring a service dead if it got over
> 40 requests / minute. A later patch from Sun (talking 4.1.x, heh)
> allowed invocation of inetd -r nn ss where nn was number of connect
> requests and ss was time frame. Don't know if Linux inetd has same
> mechanism of self-defense, your script might well trigger it.
>
> --alessandro
>
