Segfaults with some modules, positional dependent

I'm having a weird problem with certain modules causing perl scripts to segfault. The errors in the log are like [Thu May 20 03:19:31 2004] [notice] child pid 10522 exit signal Segmentation fault (11) The module causing the problems is Sys::Hostname. The perl script has the line use

Scripts with lots of output take too long

Hi everyone, I've been happily converting over a bunch of scripts to use mod_perl since we recently solved my Apache::SSI issues. My main reason for migrating to mod_perl from standard CGI scripts is to improve performance on our Web server. Many scripts take several seconds to

SOLVED: Scripts with lots of output take too long

However, I've noticed that scripts that generate lot of output take substantially longer to run than their CGI counterparts. The CGI script took 1.59 seconds to run, whereas the mod_perl version took 3.38 seconds. It generates about 321K of output. Are you positive that

Re: Using SSI with perl handlers?

What happens if you use #include virtual instead? The #exec cgi directive has been deprecated in mod_include for years. The Apache::SSI module sets the content-type to application/x-httpd-cgi when you use exec cgi, and that might be causing a problem here, since what you are including are

Re: Using SSI with perl handlers?

Basically, it all boils down to the fact that once an SSI directive with #EXEC CGI is parsed, the document fails to parse any further SSI directives *if the script to be executed has a perl-script handler.* from the manpage: * When chaining handlers via Apache::Filter, if

Re: SOLVED (was 'Using SSI with perl handlers?')

I hate to be a wet blanket, but that looks very wrong to me. Apache::PassHtml does not work with Apache::Filter, so you probably are not running Apache::SSI on these files at all. Hi Perrin, You are, of course, right. :) Apache::SSI was being used, but the Content-Type: wasn't being

Using SSI with perl handlers?

Hi, I sent out an email yesterday describing some problems that I'm having with Apache::SSI. I've narrowed things down significantly and hope that this extra info can help someone point me in the right direction. Basically, it all boils down to the fact that once an SSI directive

Apache::SSIChain stops halfway through

Hi there, I've recently started converting many of the scripts on my Web site to use mod_perl in the interest of increasing performance. I've run into a strange problem with Apache::SSI -- only the first few SSIs are processed, while the rest show up as SSI tags in the document