Hello,
I'm not sure this is a mod_perl question per se, but I'm hoping there's
a mod_perl solution to our problem.
We currently use a 3rd party security company to do a nessus-type
security audit on our site for PCI compliance. Their scans naturally
generate a lot of noise in the error log,
In message <30a2344a1001271105t6c690071qb72eb53df2a68...@mail.gmail.com>, Pas A
rgenio writes:
>I'm building everything from source. I've rebuilt perl a half-dozen times
>both static & dynamic. I'm working on building 5.10.1 but it seems so
Does modperl's make test succeed?
Under Solaris, you n
On Jan 27, 2010, at 2:45 PM, Perrin Harkins wrote:
On Tue, Jan 26, 2010 at 7:42 PM, Jonathan Swartz
wrote:
On our site we create a new CGI::Session object at the beginning of
the
request, so that it can be used anywhere in the web code.
However, sessions are rarely written to, so at the en
On Tue, Jan 26, 2010 at 7:42 PM, Jonathan Swartz wrote:
> On our site we create a new CGI::Session object at the beginning of the
> request, so that it can be used anywhere in the web code.
>
> However, sessions are rarely written to, so at the end of the request I'd
> like to avoid actually writi
Perl 5.10.1 is still relatively new, so you might want to give 5.8.9 a
shot. That is more heavily vetted on lesser used platforms such as
Solaris.
On Wed, Jan 27, 2010 at 9:28 AM, Pas Argenio wrote:
> I just fell back to Apache-2.2.8 but same problem. By the way, Tosh, how
> did you dump the li
No, wish I were. East coast US, unseasonably warm (we have more hot air in
general).
I'm building everything from source. I've rebuilt perl a half-dozen times
both static & dynamic. I'm working on building 5.10.1 but it seems so
different in the build defaults.
Still to try: mod_perl.2.0.3 and u
perl -V
I don't think it's an Apache issue, my purely superstitious feelings
based on the ravens I saw flying around this morning is that blame lies
with perl 5.10, I just don't trust even number releases, even less round
numbers cleanly divisible by 10.
But then $r scares me so...
Are you
I just fell back to Apache-2.2.8 but same problem. By the way, Tosh, how
did you dump the libperl info?
I'm getting more core dumps than you, but pages are displayed by the next
child to pick it up. Here is the most common stack trace (via Solaris'
pstack command):
Wed Jan 27 09:06:35 EST 2010
c
David E. Wheeler wrote:
On Jan 27, 2010, at 7:23 AM, Adam Prime wrote:
This smells like a UseCanonicalName On + mod_dir redirect to me. If the
directory /admin/profile/dest exists in the document root, there's a good
chance it is.
Ooh, thanks! I can see that I have mod_dir as a DSO, but I'
Just wanted to note that since you've put the CONN_CLOSE in the
redirect code, it's not necessary (nor desirable) to put
"KeepAlive Off" in apache2.conf
With the CONN_CLOSE call you turn KA off just when you need it to be
off.
So what's the bad news?
cmac
On Jan 27, 2010, at 5:08 AM, To
On Jan 27, 2010, at 7:23 AM, Adam Prime wrote:
> This smells like a UseCanonicalName On + mod_dir redirect to me. If the
> directory /admin/profile/dest exists in the document root, there's a good
> chance it is.
Ooh, thanks! I can see that I have mod_dir as a DSO, but I'm not loading it.
The
I'm seeing the same thing on my DEV server which is:
Server: Apache/2.2.11 (Ubuntu) mod_perl/2.0.4 Perl/v5.10.0
I see it in the mornings when it has been sitting around all night doing
nothing, and the first couple hits result in core dumps/seg faults, then
after pounding REFRESH like a mad mo
On Wed, Jan 27, 2010 at 8:22 AM, Tosh Cooey wrote:
> In case anyone else is ever in the same situation I would like to tell them
> that mod_perl(1|2) + fork = bad idea, and don't even THINK about throwing
> DBI into the mix.
I don't want people to think this doesn't work. It does work, and has
b
David E. Wheeler wrote:
Fellow mod_perlers,
Note that the hosthame is "benedict.local". Now I often just use localhost when
using Bricolage, and most of the time that works fine. But there is one
JavaScript-triggered redirect button that looks like this:
window.location.href = '/admin/p
Just to tie this thread up...
In case anyone else is ever in the same situation I would like to tell
them that mod_perl(1|2) + fork = bad idea, and don't even THINK about
throwing DBI into the mix.
For me in the future, if I have a VERY long task I will externalize it,
and if I have brief bu
Would this problem be any different in a normal CGI context with the
program doing forks? I don't imagine it would be, which is why I see
the ultimate wisdom in spawning an external program to handle
long-running tasks, or just cron something.
Oh well, live and learn.
Tosh
William T wrote:
The good news is that Mr. Mackenna got it! If I set "KeepAlive Off" in
apache2.conf then it all works fine. Below is a functioning long
process thingy which works with "KeepAlive On" and Firefox. I just hope
it works with MSIE ...
#!/usr/bin/perl
use strict;
use Apache2::Const -compile =>
17 matches
Mail list logo
