The following issue has been SUBMITTED. 
====================================================================== 
http://www.dbmail.org/mantis/view.php?id=449 
====================================================================== 
Reported By:                aaron
Assigned To:                aaron
====================================================================== 
Project:                    DBMail
Issue ID:                   449
Category:                   General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
target:                      
====================================================================== 
Date Submitted:             17-Nov-06 09:25 CET
Last Modified:              17-Nov-06 09:25 CET
====================================================================== 
Summary:                    Problem with fnctl O_NONBLOCK dance
Description: 

What we need to to is *force* the blocking state back on, after the
accept.

What happens in 2.2.0 is somewhat similar to what is described above: a
child has done a O_NONBLOCK when another does F_GETFL. This way, the
client socket ends up being non-blocking - which is not what the calls
to fgets expect.

So: either we make real sure the client socket is blocking, or we teach
all daemons to read from the clients in a non-blocking fashion. The
latter is what we want eventually (when we want to go async), but until
than, the first solution is simple and limited in scope.
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
17-Nov-06 09:25 aaron          New Issue                                    
17-Nov-06 09:25 aaron          Status                   new => assigned     
17-Nov-06 09:25 aaron          Assigned To               => aaron           
======================================================================

Reply via email to