[peruser] child processes dying

Leen Besselink leen at consolejunkie.net
Mon Jun 6 00:07:17 MDT 2005

On Sun, Jun 05, 2005 at 05:26:56PM -0600, Sean Gabriel Heacock wrote:
> On Mon, 2005-06-06 at 00:44 +0200, leen at wirehub.nl wrote:
> > The child processes keep dying, when started, when a request is send.
> > 
> > So far I've found out it dies in apr_os_sock_put () called from within
> > child_main () within the CHILD_TYPE_PROCESSOR-case (of the 0.52-
> > peruser-0.1.2 on Linux 2.6.11, Debian Stable/Testing, gcc 2.95.4).
> There's a major problem with 0.1.2, the accept lock isn't working so
> some requests cause it to crash (POST data gets sent to two different
> processes).  I'm not sure if that's the problem you're getting or not...
> You might want to give r10 a try, or wait for the next release (which
> I'm going to work on tonight, but I'm not sure if I'll manage to get it
> working)

Ahh, ok, I'll test it, doing a build isn't that hard, just takes some time. :-)

If I've seen it work, I might be able to say more about what's wrong with 0.1.2, who knows.

> -- 
> Sean Gabriel Heacock
> Telana Internet Services
> http://www.telana.com/

More information about the Peruser mailing list