On Wed, Sep 30, 2009 at 10:47 AM, Clinton Gormley wrote:
>> Do either of these bear any relation to mod_perl's shared memory which
>> you can use by preloading modules at startup?
>
> Yes - as I understand it (somebody please correct me if I'm wrong), all
> of the C libraries (eg XS modules) that
> i. The total VIRT size of the process before was 119 Mb
> ii. Before - the process shared 94 Mb with other processes
> iii. After - shared has gone down and private dirty up - does this
> mean that this process now 'owns' this memory and it can't be used by
> other processes?
Correct
>
> The o
On Wed 30 Sep 2009, Bernhard Janetzki wrote:
> Hello together,
> i'm trying basic authentication via
>
> ## apache2 config:
>
> SetHandler perl-script
> PerlAuthenHandler DataExchange::AuthHandler
> #PerlResponseHandler ModPerl::Registry
>
I believe what you want is:
# To set the variable so that CGI scripts can access $ENV{'REMOTE_USER'}
# which is normally populated by Basic-Auth (this is only if you want to
# take control over the variable... populating it yourself)
#
$r->subprocess_env(REMOTE_USER => $user);
# To get the variab
Hello together,
i'm trying basic authentication via
## apache2 config:
SetHandler perl-script
PerlAuthenHandler DataExchange::AuthHandler
#PerlResponseHandler ModPerl::Registry
Options +ExecCGI
PerlOptions +GlobalReques
Justin Wyllie wrote:
Hi clint
Yes. Linux and this script looks good. We've think that part of the problem
is in the modules Apache is loading so this will be useful.
I also have another couple of questions:
I have found the errant code where our process jumps by 13 Mbs. One part
does something
Hi clint
This script looks helpful. I don't completely understand (even after looking at
the documentation for Linux::Smaps) it though
Looking at this output:
##before a bit hit on an expensive part of the web site
VMSIZE: 119472 kb
RSS: 96184 kb total
94904 kb shared
