PerlOptions +Parent in Debian 8 (jessie)

Hi all, I have two servers using Debian Jessie. The first one was upgraded from Debian 7 (wheezy), the second one is a fresh install. One of my virtual hosts uses the option "PerlOptions +Parent"; no problem on the first server, but Apache won't start when this option is enabled

Re: Is "PerlOptions +Parent" per directory or not?

I use it like this inside my VirtualHost declaration: PerlOptions +Parent PerlRequire /usr/local/lariat-03.02.xx/conf/qa/startup-qa-03.02.xx.pl This allows me to use a different version of my code base and a different startup.pl on a per virtual host basis. Without it, all of my virtual hosts

Is "PerlOptions +Parent" per directory or not?

Hello, according to the docs[1] "PerlOptions +Parent" is available per directory, the example even uses a "Location" block. But if I try that, I always get the following error: > Invalid per-directory PerlOption: Parent I tried that in the past years time and again with

SIGSEGV: PerlLoadModule inside VirtualHost with PerlOptions +Parent

mconfig=0x689b60, args=0x72d618 "127.0.0.1:8000>") at config.c:757 #16 0x00441bc4 in ap_walk_config_sub (current=0x72d5d8, parms=0x7fffdb70, section_vector=0x689740) at config.c:1163 #17 0x00441c71 in ap_walk_config (current=0x72d5d8, parms=0x7f

Re: [mp2] Possible bug with "PerlOptions +Parent" with mod_perl 2.0.4 and mod_perl 2.0.5 (Ubuntu packages)

n Wed, May 8, 2013 at 11:13 PM, Luca Maranzano wrote: > Hello all, > > I've setup two instances of the popular OTRS software using the > PerlOptions +Parent to have two separate interpreter pool in 2 distinct > Virtual Hosts. > > Under Ubuntu 8.04 LTS all was working fin

[mp2] Possible bug with "PerlOptions +Parent" with mod_perl 2.0.4 and mod_perl 2.0.5 (Ubuntu packages)

Hello all, I've setup two instances of the popular OTRS software using the PerlOptions +Parent to have two separate interpreter pool in 2 distinct Virtual Hosts. Under Ubuntu 8.04 LTS all was working fine, with mod_perl2 version 2.0.3 provided by Ubuntu 8.04. I'm not sure it is a rea

Re: Getting NYTProf to work with vhosts that use PerlOptions +Parent

On Thu, Apr 29, 2010 at 04:02:05PM -0700, Fred Moyer wrote: > On Thu, Apr 29, 2010 at 4:39 AM, Tim Bunce wrote: > > On Wed, Apr 28, 2010 at 11:25:14PM -0400, Adam Prime wrote: > >> Maybe you could try doing the push_handler for the ChildExitHandler > >> when the ChildInitHandler executes?  Just a

Re: Getting NYTProf to work with vhosts that use PerlOptions +Parent

sing an END block. Devel::NYTProf::Apache does that using >> > >> >    sub child_exit { DB::_finish() } >> > >> >    my $s = Apache2::ServerUtil->server; >> >    $s->push_handlers(PerlChildExitHandler => \&child_exit); >> > >> >That works

Re: Getting NYTProf to work with vhosts that use PerlOptions +Parent

f::Apache does that using > > > >sub child_exit { DB::_finish() } > > > >my $s = Apache2::ServerUtil->server; > >$s->push_handlers(PerlChildExitHandler => \&child_exit); > > > >That works fine normally, but doesn't work with PerlOptio

Re: Getting NYTProf to work with vhosts that use PerlOptions +Parent

block. Devel::NYTProf::Apache does that using sub child_exit { DB::_finish() } my $s = Apache2::ServerUtil->server; $s->push_handlers(PerlChildExitHandler => \&child_exit); That works fine normally, but doesn't work with PerlOptions +Parent. I get an error: [

Getting NYTProf to work with vhosts that use PerlOptions +Parent

sh_handlers(PerlChildExitHandler => \&child_exit); That works fine normally, but doesn't work with PerlOptions +Parent. I get an error: [error] lookup of 'Devel::NYTProf::Apache::child_exit' failed I presume that's because the $s doesn't refer to the vhost "I'm in&q

Re: PerlOptions +Parent

On 10-02-01 06:32 , Torsten Förtsch wrote: > On Monday 01 February 2010 11:48:19 Carl Johnstone wrote: >> So rather than +Parent which just gives a VirtualHost a separate instance >> - what would be nice would be some way of specifying which perl instance >> to use in this VirtualHost. Something

Re: PerlOptions +Parent

On Monday 01 February 2010 13:23:19 Rolf Schaufelberger wrote: > Am 01.02.2010 um 12:32 schrieb Torsten Förtsch: > > On Monday 01 February 2010 11:48:19 Carl Johnstone wrote: > >> So rather than +Parent which just gives a VirtualHost a separate > >> instance - what would be nice would be some way

Re: PerlOptions +Parent

On Monday 01 February 2010 11:48:19 Carl Johnstone wrote: > So rather than +Parent which just gives a VirtualHost a separate instance > - what would be nice would be some way of specifying which perl instance > to use in this VirtualHost. Something like: > > > ServerName www.example1.com > Per

PerlOptions +Parent

owing some discussion here I tested and implemented the use of "PerlOptions +Parent" and this works just fine. However my only problem with this is that what I'm effectively doing is running a separate perl instance for each of those VirtualHosts, sometimes I'll have half a dozen -

PerlOptions +Parent and virtual hosts

Hello, I have successfully been using name-based virtual hosts and have just added "PerlOptions +Parent" as a way to have multiple branches of my codebase running on the same server. A typical virtual host is configured as: ServerNametrunk.translator.xcma.devo Docum

Re: mod_perl v2 documentation bugs: location of PerlOptions +Parent, PerlSwitches

v.html > > PerlOptions ITERATEDIR > > ...but when I add > PerlOptions +Parent > > to my apache.conf, I get the error message: >Invalid per-directory PerlOption: Parent http://perl.apache.org/docs/2.0/user/config/config.html#C_Parent_ ... seems to app

mod_perl v2 documentation bugs: location of PerlOptions +Parent, PerlSwitches

#mod_perl_Directives_Argument_Types_and_Allowed_Location PerlOptions is listed as "DIR"... PerlOptions ITERATEDIR ...but when I add PerlOptions +Parent to my apache.conf, I get the error message: Invalid per-directory PerlOption: Parent 2. PerlSwitches Doc here: http://perl.apache.or

Re: [mp2] block & PerlOptions +Parent & PerlRequire segfaults on 2.0.2, but not 2.0.1

Eamon Daly wrote: > This patch worked like a charm for me. Thanks for the quick > response! Great, then a slightly different patch has been applied to SVN in change 371775, documented in change 371776 Now there are 2 identical ways to specify Switch inheritance: - PerlSwitches +inherit (the old

Re: [mp2] block & PerlOptions +Parent & PerlRequire segfaults on 2.0.2, but not 2.0.1

Cc: ; Sent: Friday, January 20, 2006 7:53 PM Subject: Re: [mp2] block & PerlOptions +Parent & PerlRequire segfaults on 2.0.2, but not 2.0.1 Eamon Daly wrote: 1. Problem Description: If I declare a section in httpd.conf, then define a virtual host with "PerlOptions +Pare

Re: [mp2] block & PerlOptions +Parent & PerlRequire segfaults on 2.0.2, but not 2.0.1

Eamon Daly wrote: > 1. Problem Description: > > If I declare a section in httpd.conf, then define > a virtual host with "PerlOptions +Parent", httpd dies with > a segfault on subsequent PerlRequires. This works in 2.0.1. > Here's a minimal example, tack

[mp2] block & PerlOptions +Parent & PerlRequire segfaults on 2.0.2, but not 2.0.1

1. Problem Description: If I declare a section in httpd.conf, then define a virtual host with "PerlOptions +Parent", httpd dies with a segfault on subsequent PerlRequires. This works in 2.0.1. Here's a minimal example, tacked on to the end of the default httpd.conf: --- htt

PerlOptions +Parent and Virtual Hosts problem

I noticed two problems (possibly just documentation issues?) when playing with PerlOptions +Parent and virtual hosts: 1) PerlSwitches -Mlib and -I were completely ignored within the VirtualHost tags And more importantly... 2) I have 3 virtual hosts (not NameVirtualHosts, but separate IPs