[suPHP] Suphp hangs when php script sends 4097 bytes of data to stderr

[Jeremy Chadwick]

This looks pretty severe -- I don't care what the Debian developers
have to say ("is this really grave? why should a script be sending
anything to stderr").  In fact, I would classify this as critical.

This seems like a libc thing.  The fact that >4096 plays a role
is something to focus on.  I can't remember the specifics (sigh,
this morning has been crazy!), but I believe stdout/in/err all
block when there's more than 4096 bytes on the descriptor.  It's
the applications' job to fflush() them, or use select() to handle
things appropriately.  (I feel like I'm talking out of my arse...)

I'll have someone who's more familiar with this aspect take a peek
at the problem.  I'll also see if I can reproduce this on our
production FreeBSD boxes.

-- 
| Jeremy Chadwick                                 jdc at parodius.com |
| Parodius Networking                        http://www.parodius.com/ |
| UNIX Systems Administrator                   Mountain View, CA, USA |
| Making life hard for others since 1977.               PGP: 4BD6C0CB |

On Sun, Sep 10, 2006 at 08:45:21AM +0200, Emmanuel Lacour wrote:
> 
> I forward this bug (reported to the debian package) as I'm not able to
> solve it myself. Can one of the suphp devs look at it?
> 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=382086
> 
> 
> -- 
> Emmanuel LACOUR - elacour at home-dn.net
> 
> _______________________________________________
> suPHP mailing list
> suPHP at lists.marsching.biz
> http://lists.marsching.biz/mailman/listinfo/suphp