www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <dgau...@apache.org>
Subject Re: config/467: possible starved listening sockets -- httpd stops responding
Date Thu, 24 Apr 1997 11:10:00 GMT
The following reply was made to PR config/467; it has been noted by GNATS.

From: Dean Gaudet <dgaudet@apache.org>
To: apbugs@apache.org
Subject: Re: config/467: possible starved listening sockets -- httpd stops responding
Date: Thu, 24 Apr 1997 04:02:16 -0700 (PDT)

 
 Addendum:  If you have problems using -DUSE_FLOCK_SERIALIZED_ACCEPT then
 you can also try -DUSE_FCNTL_SERIALIZED_ACCEPT.
 
 Dean
 
 On Thu, 24 Apr 1997, Dean Gaudet wrote:
 
 > 
 > >Number:         467
 > >Category:       config
 > >Synopsis:       possible starved listening sockets -- httpd stops responding
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    apache (Apache HTTP Project)
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   apache
 > >Arrival-Date:   Thu Apr 24 04:00:01 1997
 > >Originator:     dgaudet@apache.org
 > >Organization:
 > apache
 > >Release:        1.2
 > >Environment:
 > All that do not USE_xxxxx_SERIALIZED_ACCEPT.
 > >Description:
 > It is possible on architectures that do not USE_xxxxx_SERIALIZED_ACCEPT
 > to freeze out some listening sockets when multiple Listen directives
 > are used.  The workaround is to add -DUSE_FLOCK_SERIALIZED_ACCEPT to
 > the EXTRA_CFLAGS line in the Configuration file.
 > 
 > See src/conf.h to determine if your architecture is affected.  This affects
 > many architectures.
 > >How-To-Repeat:
 > 
 > >Fix:
 > The permanent fix will likely involve using non-blocking listening sockets.
 > But experimentation is needed to determine if it's faster to serialize
 > accept()s than it is to deal with potentially many EAGAIN/EWOULDBLOCKs
 > >Audit-Trail:
 > >Unformatted:
 > 
 > 
 > 
 

Mime
View raw message