Sorry for the delayed Summary as I was out of contact with the keyboard
for sometime.
On Wed, 25 Nov 1992 Subramanian.Kumaraswamy.1@nd.edu wrote:
>
> Hello Sun managers,
> The famous inetd gets into a zombie/frozen state once in a while(last
> time it happened was 3 months back). Even the SIGHUP signal wouldn't
> do any good and the only alternative I found was to restart the inetd.
> Since there are lot of servers running on that machine from inetd,
> this is a serious problem for us.
>
>.............
I got one reply from Glenn Satchell and it addressed the bug("feature"?) which
I was aware of and I forgot to mention in my original posting though I
indirectly mentioned about sending "SIGHUP" to inetd which can be
considered as a temporary solution until you are haunted by the bug again
Please see the appended README file for the bug info and the fix.
The problem we are facing is a total inetd freeze and the bug fix won't
help us anyway. This means the bug we are facing still lives and have no
clues yet.
Thanks to Glenn Satchell(ups!glenn@fourx.Aus.Sun.COM) for sending the README
file of the Patch.
---------------------------CUT HERE---------------------------------------
Patch-ID# 100178-07
Keywords: broken server detection
Synopsis: SunOS4.0.3;4.1;4.1.1;4.1.2;4.1.3: inetd "broken server
detection" brea
ks on fast machines
Date: 28/Aug/91
SunOS release: 4.0.3, 4.1, 4.1_PSR_A, 4.1.1, 4.1.2 4.1.3
Unbundled Product:
Unbundled Release:
Topic: Patch revision adds 4.1.3 compatibility
BugId's fixed with this patch: 1030599
Architectures for which this patch is available: sun3 sun3x sun4 sun4c sun4m
Patches which may conflict with this patch:
Obsoleted by: SunOS 5.0
Update -07 [10-Mar-92 and 22-Sep-92]
Added 4.1.2 {and 4.1.3}/sun4,sun4c, and sun4m object module. The source
code did not change.
Update -06 [28-Aug-91]
updated the sun4PSR_A object module. The source code did not change.
_________________________________________________________________________
Problem Description:
inetd refuses to accept more than 40 connects per minute on a
particular socket (loop detection)
The SS1 is fast enough, that you can end up legitimately calling
rsh more than 40 times per minute.
This patch adds a new argument, "-r", to inetd that allows you to
specify number of connections allowed in the given time in seconds.
The default is to allow 40 connections in a 60 second period, E.G:
/usr/etc/inetd -r 40 60
Typically for a faster machine you might up this to 60 connections
per minute, E.G:
/usr/etc/inetd -r 60 60
You will need to edit /etc/rc to make the change permanent each
time the machine is rebooted, E.G:
...
...
if [ -f /usr/etc/inetd ]; then
inetd -r 60 60; echo -n ' inetd'
fi
...
...
---------------------END README---------------------------------------
Subra
___________________________________________________________________________
subramanian kumaraswamy Kawa' 550 -!0!- Voice: (219) 239-8590
Office of Univ. Computing _//*= e-mail:subra@nd.edu
Univ. of Notre Dame @\__/#/%/ \\ FAX:(219) 239-8201
Notre Dame IN 46556 .....==(0)_/h/ (0)
___________________________________________________________________________
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:06:54 CDT