Re: go crazy with me

Not sure what you mean by it not scaling - can you elaborate? Sure it uses more ram than multiplexing, but even for a high traffic mail server like apache.org's the mail-in-apache2 model works well (apache.org uses Apache::Qpsmtpd for email). I'm curious as to how you've mixed things up

Solving mod_perl scalability issues for lots of slow connections

[note: Subject changed from go crazy with me -- LoL] I'd also like to hear what people are doing when the apache model has scaling problems. We have one problematic project here: we're a gateway and must server a high number of very slow customers to a high number of very slow feeds. Ideally

Re: go crazy with me

Okay, so you basically run two daemons -- mod_perl, and a separate multiplexing one -- to handle this? Did you investigate what would be involved in changing apache to support multiplexing as an MPM? Yes -- we did look at that. The problem is that the MPM model assumes that the handler runs

Re: UDP Protocol Handler?

Matt Sergeant [02/08/05 10:42 -0400]: On 20 Jul 2005, at 10:40, Dan Sully wrote: Has anyone written a protocol handler for UDP? If so - could you share any examples? I haven't, but IIRC there is/was a talk at YAPC::EU about using mod_perl as a DNS server... I think it is by mock,

Re: [MP2] pseudo_http.pm tests fail under FreeBSD/Jail

://www.knowmad.com -- MailChannels: Assured Messaging -- Eliminate Critical False Positives http://www.mailchannels.com MailChannels Corporation Suite 1600, 1188 West Georgia St. Vancouver, BC, Canada Ken Simpson, CEO +1-604-729-1741 Sent by MailChannels: http://www.mailchannels.com

Re: [MP2] pseudo_http.pm tests fail under FreeBSD/Jail

call ... therefore the blocking state never actually changed. TTUL Ken -- MailChannels: Assured Messaging -- Eliminate Critical False Positives http://www.mailchannels.com MailChannels Corporation Suite 1600, 1188 West Georgia St. Vancouver, BC, Canada Ken Simpson, CEO +1-604-729-1741 Sent

Debugging Out of Memory Errors

://www.mailchannels.com MailChannels Corporation Suite 1600, 1188 West Georgia St. Vancouver, BC, Canada Ken Simpson, CEO +1-604-729-1741 Sent by MailChannels: http://www.mailchannels.com

Success Story

(I'm reposting this -- but in the format suggested on the success stories page; apologies for the spam) URL: http://www.mailchannels/opensource/ Title: Running email through mod_perl Contact Person: Ken Simpson [EMAIL PROTECTED] Traffic: Low (in development) Success Story: We have been using

Re: mod_perl marketing

MailChannels Corporation Suite 1600, 1188 West Georgia St. Vancouver, BC, Canada Ken Simpson, CEO +1-604-729-1741 Sent by MailChannels: http://www.mailchannels.com -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http

Re: [mp2] NetBSD-1.6.2 modperl 1.99_16 httpd 2.0.51-dev make test errors

West Georgia St. Vancouver, BC, Canada Ken Simpson, CEO +1-604-729-1741 Sent by MailChannels: http://www.mailchannels.com -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email

Re: [mp2] NetBSD-1.6.2 modperl 1.99_16 httpd 2.0.51-dev make test errors

to an ephemeral port fails on OpenBSD so override # the test for O_NONBLOCK inheritance across accept(). APR_SETIFNULL(ac_cv_o_nonblock_inherited, [yes]) ... I don't know about NetBSD or OSX. TTUL Ken Stas Bekman [17/09/04 18:35 -0400]: Ken Simpson wrote: So is that the right

Re: [mp2] NetBSD-1.6.2 modperl 1.99_16 httpd 2.0.51-dev make test errors

: Invalid argument -- MailChannels: Imagine no more spam -- http://www.mailchannels.com MailChannels Corporation Suite 1600, 1188 West Georgia St. Vancouver, BC, Canada Ken Simpson, CEO +1-604-729-1741 -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist

Re: [mp2] NetBSD-1.6.2 modperl 1.99_16 httpd 2.0.51-dev make test errors

know if it works for you and cc the Apache APR dev list. TTUL Ken -- MailChannels: Imagine no more spam -- http://www.mailchannels.com MailChannels Corporation Suite 1600, 1188 West Georgia St. Vancouver, BC, Canada Ken Simpson, CEO +1-604-729-1741 -- Report problems: http://perl.apache.org

Re: [mp2] Test failures with APR::Socket

mod_perl. It should work. TTUL Ken -- MailChannels: Imagine no more spam -- http://www.mailchannels.com MailChannels Corporation Suite 1600, 1188 West Georgia St. Vancouver, BC, Canada Ken Simpson, CEO +1-604-729-1741 -- Report problems: http://perl.apache.org/bugs/ Mail list info: http

Re: APR::Poll support -- first cut

I was thinking, would it be better to make it an APR::Socket method? $socket-poll($c-pool, 1_000_000, APR::POLLIN); looks more intuitive to me. Especially since you've hardcoded the fd type to be socket: fd.desc_type = APR_POLL_SOCKET; That's a really good idea. I'll move it into

Re: APR::Poll support -- first cut

I have no problem removing the copyright from the patch. I will be changing the patch slightliy to implement Stas's suggestion of $socket-poll() instead of APR::Poll-poll(). When I submit that patch, there will be no copyright. Nonblocking sockets shall take precedence over hourly billing lawyers

APR::Poll support -- first cut

and a specified timeout. + * + * The pollset_* methods have not been included (they allow you to poll + * multiple sockets at one time. Nor has the ability to poll a file been + * provided because it's assumed that within, say, a protocol handler, + * you'd probably never need to. + * + * -- Ken

mod_perl 1.99_16 tests fail on OpenBSD due to low open files limit

FYI, I just discovered after much pain and suffering that the mod_perl test suite fails to run on OpenBSD 3.5 because it tries to open more than 64 files at once. To duplicate, try this on your OpenBSD box: $ sudo ktrace -d /usr/local/apache2.0.50-modperl1.99_16/bin/httpd -d \

[mp2] Protocol handler tests fail in 1.99_16 with Apache 2.0.50

LWP: 5.76 mod_perl : 1.9916 3. This is the core dump trace: (if you get a core dump): [CORE TRACE COMES HERE] This report was generated by t/REPORT on Wed Aug 25 22:14:03 2004 GMT. -- MailChannels: Control Your Email http://www.mailchannels.com Ken Simpson, CEO +1-604-729

Re: mod_perl 1.99_16 tests fail on OpenBSD due to low open files limit

://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html -- MailChannels: Control Your Email http://www.mailchannels.com Ken Simpson, CEO +1-604-729-1741 -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org

Re: mod_perl 1.99_16 tests fail on OpenBSD due to low open files limit

://www.mailchannels.com Ken Simpson, CEO +1-604-729-1741 -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html

Re: [mp2] Protocol handler tests fail in 1.99_16 with Apache 2.0.50

Hmm, may be it reports blocking when it's not. What if you replace the whole blocking testing/setting conditional block, with just unconditional: $socket-opt_set(APR::SO_NONBLOCK = 0); I have tried this and it makes no difference -- it looks like non blocking mode is simply not being set.

Re: [mp2] Protocol handler tests fail in 1.99_16 with Apache 2.0.50

I have tried this and it makes no difference -- it looks like non blocking mode is simply not being set. And this verification code doesn't fail? # test that we really *are* in the blocking mode !$socket-opt_get(APR::SO_NONBLOCK) or die failed to set

Re: [mp2] Protocol handler tests fail in 1.99_16 with Apache 2.0.50

I'm tracing through the Apache code to see what's actually happening. Ouch. Notice that apr-1.0 can be released any moment now. So please post a notice to the apr-dev list if you find what the problem is. Okay -- I'll do that. Great. I'll look at the patch. There are no relevant diffs

Re: [mp2] Protocol handler tests fail in 1.99_16 with Apache 2.0.50

Oh, so may be it was always broken. Didn't you say that the problem was introduced in Apache 2.0.50? It seemed that way, but I think that it actually died in 0.49. I'm trying with 0.48. TTUL Ken -- Report problems: http://perl.apache.org/bugs/ Mail list info:

Re: How to tell if there's data waiting on a NON-blocking Apache connection?

-- MailChannels: Control Your Email http://www.mailchannels.com Ken Simpson, CEO +1-604-729-1741 -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html

Re: How to tell if there's data waiting on a NON-blocking Apache connection?

apr_os_sock_get() to get the fd. What would this incantation look like in Perl-land? TTUL Ken -- MailChannels: Control Your Email http://www.mailchannels.com Ken Simpson, CEO +1-604-729-1741 -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html

Re: How to tell if there's data waiting on a NON-blocking Apache connection?

://www.mailchannels.com Ken Simpson, CEO +1-604-729-1741 -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html

How to close a socket when all you have in an Apache::Connection object

-- MailChannels: Control Your Email http://www.mailchannels.com Ken Simpson, CEO +1-604-729-1741 -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html

How to tell if there's data waiting on a NON-blocking Apache connection?

Your Email http://www.mailchannels.com Ken Simpson, CEO +1-604-729-1741 -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html

Re: How to tell if there's data waiting on a NON-blocking Apache connection?

could give it a shot! TTUL Ken -- MailChannels: Control Your Email http://www.mailchannels.com Ken Simpson, CEO +1-604-729-1741 -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email