On Wed, 2005-08-24 at 10:31 +1000, Badai Aqrandista wrote:
> Anyway, to fix this, I'm trying to make my onw shared memory with
> Apache::SharedMem.
Don't use that module. It's very inefficient.
> But it seems that shared memory is just a memory area
> that any process can read from or write to
Tom Schindl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I went back to my 2.0.40 install of Apache. The 2.0.54 was not playing
nice with plesk. How do I update the @INC path and/or mod_perl for the
new perl 5.8.7? I try using CPAN with install Bundle::Apache and no go.
Any ideas?
Philip M. Gollucci wrote:
In mp2 I am doing this:
---
use Apache2::ServerRec ();
use Apache2::ServerUtil ();
my $s = Apache2::ServerUtil->server();
warn "port = ",$s->port(),"\n";
Try
use Apache2::RequestUtil ();
Apache2::RequestUtil->request()->get_server_port()
Though I d
On Tue, 2005-08-23 at 17:23 +1000, Badai Aqrandista wrote:
> How do I maintain the size of the shared memory between apache children?
> What cause a memory page to be copied (not shared) from perl's point of
> view?
Anything that writes to memory -- modifying any variable (even just
reading one i
Sounds great, it'd be a nice addition to Apache2::Cookie. Getting the
secret through to freeze and thaw is the tricky bit - I guess it could
just be supplied to fetch() and new().
There are a couple of extras that I'm adding:
- a delete method which deletes the cookie by name (ie. you don't ha
Having it validate the cookie based on a hash on data+ server secret is
a great addition.
I've been doing that already on a custom abstraction class for
Apache::Cookie as well -- i needed to build something that would switch
the cookie baking code to either use headers_out or bake on the fly
On Tuesday 23 August 2005 21:08, Philip M. Gollucci wrote:
> One comment might be to add an option to turn it off even if the newer
> Smaps support is present?
I have also thought of it. Sounds sound.
I'll send a patch soon.
Torsten
pgpKu6J3Mu1CO.pgp
Description: PGP signature
Torsten Foertsch wrote:
On Tuesday 23 August 2005 14:23, Perrin Harkins wrote:
However, you should be aware that a few months back we discovered that
our methods for measuring shared memory didn't work very well on Linux
2.4 kernels and don't really work at all on 2.6 kernels, so there may be
m
Thanks for the feedback Philip.
I believe it does subclass APR::Request::Cookie but I just left in all
the 'use' statements from Apache2::Cookie. I figured the APR::
namespace would be the wrong place for it too.
It need to override so many methods because they need to get the
RequestRec ob
Fowarding to apreq-dev (at) apache.org
Did you really need to override all those methods? Granted I haven't looked at
it that closely.
The bigest thing I would say is you should subclass perhaps
APR::Request::Cookie instead as
that is the API we recommend these days.
John ORourke wrote:
Hi
Hi folks,
I found the available cookie methods a bit tricky to use (I think the
blessed scalars or overloading were confusing me!), so I wrote a simple
cookie interface to use in place of Apache2::Cookie. Most of the code
is copied from that.
I haven't got time to CPAN-ify it at the mo, but
On Tue, 23 Aug 2005, Steve Baker wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| As Perrin mentioned, this may not be a problem with mod_perl
| specifically, so it may be worth asking on the soap-lite
| mailing list. Just to verify this, I've placed at
| http:/
Sorry, the subject on my first post probably obscured the fact that this
was a new problem post.
-8<-- Start Bug Report 8<--
1. Problem Description:
make test fails on t/modperl/request_rec_tie_api.t .
# Running under perl version 5.006002 for hpux
# Curre
On Tuesday 23 August 2005 14:23, Perrin Harkins wrote:
> However, you should be aware that a few months back we discovered that
> our methods for measuring shared memory didn't work very well on Linux
> 2.4 kernels and don't really work at all on 2.6 kernels, so there may be
> more sharing (via cop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| As Perrin mentioned, this may not be a problem with mod_perl
| specifically, so it may be worth asking on the soap-lite
| mailing list. Just to verify this, I've placed at
| http://people.apache.org/~randyk/
| a file, bug-
On Tue, 2005-08-23 at 17:23 +1000, Badai Aqrandista wrote:
> How do I maintain the size of the shared memory between apache children?
> What cause a memory page to be copied (not shared) from perl's point of
> view?
Anything that writes to memory -- modifying any variable (even just
reading one i
On Tue, 2005-08-23 at 15:52 +1000, Badai Aqrandista wrote:
> RAM = 700 Mb
> Per process total size = 40 Mb
> Shared memory = 7 Mb
>
> So, the number of processes = (700 - 7) / 33 = 21 processes
>
> So, does that mean it can only accept up to 21 connections?
Yes. If you are running a reverse pro
I think I have to reword the question:
How do I maintain the size of the shared memory between apache children?
What cause a memory page to be copied (not shared) from perl's point of
view?
This brings the question of how to increase shared memory usage. I've tried
to load every modules upf
18 matches
Mail list logo
