For the sake of the archives, let me round this thread off by saying
that I eventually got it working.
XAMPP was causing a little grief - and after a little digging around
inspired by the input from this list, I found this buried deep in the
XAMPP forums relating to another problem.
I added
Alan R Williamson wrote:
Can you double-check that these are running through ModPerl::Registry,
and not CGI? Printing out the value of $ENV{MOD_PERL} is a simple way
to do it.
oooh its blank. i take it thats not good!
That means you've been running these scripts through mod_cgi, not
mod_p
Perrin Harkins wrote:
Alan R Williamson wrote:
When i hit the .cgi pages, with perl in them, they run fine, so perl
is definitely being triggered.
Can you double-check that these are running through ModPerl::Registry,
and not CGI? Printing out the value of $ENV{MOD_PERL} is a simple way
to
Alan R Williamson wrote:
When i hit the .cgi pages, with perl in them, they run fine, so perl is
definitely being triggered.
Can you double-check that these are running through ModPerl::Registry,
and not CGI? Printing out the value of $ENV{MOD_PERL} is a simple way
to do it.
- Perrin
Yes, that should be one of the first ( if not the first ) log message
you see on server startup.
Have you tried running this with a single Apache process ( -X ) to
see if you get different results?
Yes, i tried that, and it didn't make any difference.
When i hit the .cgi pages,
On Mon, 18 Dec 2006 15:35:54 +
Alan R Williamson <[EMAIL PROTECTED]> wrote:
> Still struggling with this sadly.
>
> Frank, i tried what you said, but still no different.
>
> however, when i shutdown Apache i get this:
> _
>
> XAMMP: Stopping Apach
Still struggling with this sadly.
Frank, i tried what you said, but still no different.
however, when i shutdown Apache i get this:
_
XAMMP: Stopping Apache
[notice] Apache:DB initialized in child 32021
_
On Thu, 14 Dec 2006 17:29:39 +
Alan R Williamson <[EMAIL PROTECTED]> wrote:
> __ httpd.conf __
>
>
> PerlModule Apache::DProf
> PerlModule Bundle::Apache2
>
Echoing Perrin's last E-mail, I'm thinking maybe the:
PerlModule Bundle::Apache2
bei
Alan R Williamson wrote:
I have only got 5 child processes running, and i am looking at every
single directory for each of them, and nothing. Just the headers.
So its not that i am missing the one client that is logging. Its just
not working.
Did you check permissions to make sure that the
It gets run by the interpreter that mod_perl was compiled with. That's
not the issue though. Apache::DProf dumps out a file for every apache
child process. If you only send one request, then only one of them will
record anything. That's why I suggested sending a few hundred requests
with ab
Alan R Williamson wrote:
oooh now that is a good detective work ... now why would that be he asks?
The page renders okay on the browser, they are .cgi files that have the
PERL path at the top.
Which PERL will run that CGI page? The one referenced in the page, or
the one that Apache knows ab
oooh now that is a good detective work ... now why would that be he asks?
The page renders okay on the browser, they are .cgi files that have the
PERL path at the top.
Which PERL will run that CGI page? The one referenced in the page, or
the one that Apache knows about?
Perrin Harkins wrot
Alan R Williamson wrote:
dprofpp produces nothing ... but the tmon.out has content in it worth
444 bytes
That's just header stuff, basically. It looks like this child process
never saw a request.
- Perrin
Can you expand on that a little? What does it mean that they "never
contain anything useful"? Can you show us some dprofpp output?
Thanks for getting back to me.
dprofpp produces nothing ... but the tmon.out has content in it worth
444 bytes
___
Alan R Williamson wrote:
the files are being created, with content. That isn't the problem.
Can you expand on that a little? What does it mean that they "never
contain anything useful"? Can you show us some dprofpp output?
- Perrin
On 12/14/06, Alan R Williamson <[EMAIL PROTECTED]> wrote:
> Check the permissions to see if the user your server runs as can write
> to the profile directory.
>
> If you shut down after 1 request, only one of them will have anything
> useful in it. You might want to run ab or something to hit t
Check the permissions to see if the user your server runs as can write
to the profile directory.
If you shut down after 1 request, only one of them will have anything
useful in it. You might want to run ab or something to hit them all a
few times at the same URL.
the files are being created
Alan R Williamson wrote:
I am trying to profile CGI scripts and I am starting the server, and
shutting it down before I look at the dmon files. Of which they never
contain anything useful.
Check the permissions to see if the user your server runs as can write
to the profile directory.
If y
18 matches
Mail list logo
