Re: global variable

m...@normalperson.e4ward.com wrote: Hello, Is there a method to setup a global variable for all modperl child processes? Also this variable will be updated sometime, when it get updated, all processes will know it. As a general answer, no. That is because each child has its own separate perl i

global variable

Hello, Is there a method to setup a global variable for all modperl child processes? Also this variable will be updated sometime, when it get updated, all processes will know it. Thanks.

RE: Best way to pass arguments to an Apache2::SubProcess?

Environment variables have size limits - you should pass it as the args reference because of that, and the fact that you're sending a pointer rather than the whole data helps too, though the system is probably copying it somewhere in there you shouldn't have to worry about it. The point they're

Best way to pass arguments to an Apache2::SubProcess?

So my will has crumbled, mostly because I'm probably not very good at the "resident in memory" part of mod_perl and I will be using Apache2::SubProcess to fire off a sub-process. There seems to be two easy ways to send data to my detached sub-process; via an \...@args or via $r->subprocess_env

Re: [mp2] Apache2::SizeLimit should be using $s->rss, not $s->size for Linux::Smaps

Can you submit these patches inline? http://perl.apache.org/docs/2.0/devel/help/help.html#Submitting_Patches When they are attachments like this, people tend to not read them. Whereas when they are inline, people tend to be able to read them and comment very easily. On Tue, Feb 2, 2010 at 1:58 P

[mp2] Apache2::SizeLimit should be using $s->rss, not $s->size for Linux::Smaps

All of my processes kept exiting with a report that they had a 300M unshared size, which was clearly untrue, even from looking at top. After some investigation, I discovered that Apache2::SizeLimit was calling $s->size on the Linux::Smaps object, when instead it should be returning $s->rss