Is it ok to run a /cgi-bin/ ScriptAlias directory for mod_cgi in the
same 
VirtualHost that ModPerl::Registry is also handling a /perl/ directory 
for?  It seems to work ok for the first 10 or 20 vhosts, but 
mod_perl breaks after 30 or 40 entries.  This is an example of what I'm
doing:

<VirtualHost ###.###.##.##>

    ServerAdmin [EMAIL PROTECTED]
    DocumentRoot /web/webname/htdocs
    ServerName webname.domain.com

<Directory "/web/webname/htdocs">
     Options FollowSymLinks Includes Indexes
</Directory>

#   Will use mod_perl

    Alias /perl/ "/web/webname/perl/"
<Location /perl/>
    SetHandler perl-script
    PerlResponseHandler ModPerl::Registry
    PerlOptions +ParseHeaders
    Options +ExecCGI
</Location>

    ScriptAlias /cgi-bin/ "/web/webname/cgi-bin/"

    ErrorLog "|/apps/cronolog/1.6.2/sbin/cronolog -S 
/web/webname/logs/error
_log -P /web/webname/logs/error_log.previous 
/web/webname/logs/error_log.%Y.wk%W"

    CustomLog "|/apps/cronolog/1.6.2/sbin/cronolog -S 
/web/webname/logs/acce
ss_log -P /web/webname/logs/access_log.previous 
/web/webname/logs/access_log.%Y.wk
%W" common

    CustomLog "|/apps/cronolog/1.6.2/sbin/cronolog -S 
/web/webname/logs/refe
rer_log -P /web/webname/logs/referer_log.previous 
/web/webname/logs/referer_log.%Y
.wk%W" referer

    CustomLog "|/apps/cronolog/1.6.2/sbin/cronolog -S 
/web/webname/logs/agen
t_log -P /web/webname/logs/agent_log.previous 
/web/webname/logs/agent_log.%Y.wk%W"
 agent

</VirtualHost>

Reply via email to