Received: (qmail 17548 invoked by uid 2012); 25 Mar 1999 15:39:13 -0000
Message-Id: <19990325153913.17547.qmail@hyperreal.org>
Date: 25 Mar 1999 15:39:13 -0000
From: Sevo Stille <sevo@inm.de>
Reply-To: sevo@inm.de
To: apbugs@hyperreal.org
Subject: NO_LINGCLOSE not required for current IRIX rev's
X-Send-Pr-Version: 3.2

>Number:         4126
>Category:       os-irix
>Synopsis:       NO_LINGCLOSE not required for current IRIX rev's
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          feedback
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Thu Mar 25 07:40:00 PST 1999
>Closed-Date:
>Last-Modified:  Wed Jun 07 14:12:52 PDT 2000
>Originator:     sevo@inm.de
>Release:        1.3.6
>Organization:
>Environment:
IRIX 6.5.3, 6.* with Network rollup #7 (e.g. patch 3577 for 6.4) installed
>Description:
With 6.5.3 or Network rollup patch #7, IRIX finally properly times out 
connections in FIN_WAIT_2 under all circumstances. Successfully tried 
on several servers with peak loads beyond 1000 simultaneous connections. 
>How-To-Repeat:

>Fix:
NO_LINGCLOSE probably should not be the default any more for IRIX. 
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open-feedback
State-Changed-By: dgaudet
State-Changed-When: Tue Apr 20 12:47:23 PDT 1999
State-Changed-Why:
Hmm, if you can supply a patch which makes the decision at
compile time... then maybe we'll remove it.  But when you
say "rollup #foo" I get really worried about turning it
off as default.  It's only been about 3 years since SGI
has known of the problem, nice of them to finally decide
to fix it.  I think we can wait another year for some more
folks to start running the fixed code before we change the
default.

Dean
Comment-Added-By: coar
Comment-Added-When: Wed Jun  7 14:12:52 PDT 2000
Comment-Added:
[This is a standard response.]
This Apache problem report has not been updated recently.
Please reply to this message if you have any additional
information about this issue, or if you have answers to
any questions that have been posed to you.  If there are
no outstanding questions, please consider this a request
to try to reproduce the problem with the latest software
release, if one has been made since last contact.  If we
don't hear from you, this report will be closed.
If you have information to add, BE SURE to reply to this
message and include the apbugs@Apache.Org address so it
will be attached to the problem report!
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]