Section ENV Variables?
mod_perl = 1.27 I am trying to setup a section in my httpd.conf file that will retrieve the web server's environment variables. I've tried several methods and all lead me back to the same problem. I first tried using PerlPassEnv but could never get any environment variables from it. I also understand there is a great deal more overhead using this method. I then tried using $r->subprocess_env but always received an error regarding Can't call method "subprocess_env"on an undefined value. I believe this routine is a part of the Apache module. I verified that it was in the perl lib path and then attempted to "use" it in the section. I finally tried using $r->parsed_uri but, again, continue to receive an error regarding Can't call method "parsed_uri" on an undefined value. The routine is part of the Apache::URI module, which I verified was in the path and then attempted to "use" in the section. I am having a heck of a time trying to get the web server environment variables via the section. I could really use some assistance trying to hammer this out. I was able to get routines from the CGI module to work in the section within my httpd.conf file. I would appreciate it if someone could confirm that it is possible to read environment variables within a section with sample code. Thank you for your assistance. Respectfully, Gary -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Re: Section ENV Variables?
Geoffrey,
My intention is to capture HTTPS requests as they come in, break the URI
down, and then dynamically change DocumentRoot, Logs, etc based on
whether a given URI meets my set of criteria.
Example:
http://domain.tld = DocumentRoot /home/domain.tld/htdocs
https://secure.provider.tld/secure/domain.tld/
URI is parsed for ^/secure/([.]*[\.]+[.]*)/(.*)
DocumentRoot is then dynamically replaced with $1
I was trying to use mod_rewrite and mod_vhost_alias to do this, but I
just could not get the environment variables into DocumentRoot.
I thought this might be possible with sections?
Thank you for your assistance.
Respectfully,
Gary
Geoffrey Young wrote:
Gary C. New wrote:
mod_perl = 1.27
I am trying to setup a section in my httpd.conf file that will
retrieve the web server's environment variables. I've tried several
methods and all lead me back to the same problem.
I first tried using PerlPassEnv but could never get any environment
variables from it. I also understand there is a great deal more
overhead using this method.
I then tried using $r->subprocess_env but always received an error
regarding Can't call method "subprocess_env"on an undefined value. I
believe this routine is a part of the Apache module. I verified that it
was in the perl lib path and then attempted to "use" it in the
section.
I finally tried using $r->parsed_uri but, again, continue to receive an
error regarding Can't call method "parsed_uri" on an undefined value.
The routine is part of the Apache::URI module, which I verified was in
the path and then attempted to "use" in the section.
all of this makes me think that you're after things like $ENV{REMOTE_USER}
and other CGI environment variables?
in general, sections within a httpd.conf are executed when Apache is
started. that means that there is no request to associate with a client, so
no $ENV{REMOTE_USER} or other things make any sense. that's also why you
couldn't call $r->subprocess_env or $r->parsed_uri - there is no $r at
config time.
so, if it's these environment variables you're looking for, you'll need to
take a step back and assess what you're really trying to do.
if you're after other things - such as variables from /etc/profile - but
can't access them in sections that's a different issue, and something
that I'd need to try and recall, as I thought they should be visible at that
point.
--Geoff
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Re: Section ENV Variables?
Definitely looks like the code I'm after. I guess what is unclear to me is how to implement it. suburbanantihero states that the sections are only configurable on load time. So I would need to bind it as a handler to the ssl virtualhost section. Is this correct? I am not sure how this would then be invoked. Would it require further extension to my URI? I appreciate the help. Respectfully, Gary Geoffrey Young wrote: http://domain.tld = DocumentRoot /home/domain.tld/htdocs https://secure.provider.tld/secure/domain.tld/ URI is parsed for ^/secure/([.]*[\.]+[.]*)/(.*) DocumentRoot is then dynamically replaced with $1 I was trying to use mod_rewrite and mod_vhost_alias to do this, but I just could not get the environment variables into DocumentRoot. see recipe 4.3 in the mod_perl developer's cookbook, which is available for free from here http://www.webreference.com/programming/perl/cookbook/chap4/2.html and the code is here http://www.modperlcookbook.org/code/ch04/Cookbook/Userdir.pm but you'll also want to read up on translation handlers and the request cycle in general http://www.modperlcookbook.org/ HTH --Geoff -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Re: Section ENV Variables?
Geoffrey, I want to thank you again for pointing me in the right direction! With the sample code, I've been able to put together a semi-working module that allows me to regex the incoming uri and rewrite the DocumentRoot on the fly. This is some cool stuff. I've run into a minor problem with php_value include_path for some of my php sites. I need to find out if there are any modules in existence that will allow me to update php_value include_path on the fly like I did with document_root. I'll start a separate thread in this group with that question. Thanks again for the great pointers. Respectfully, Gary Geoffrey Young wrote: Gary C. New wrote: Definitely looks like the code I'm after. I guess what is unclear to me is how to implement it. it's a PerlTransHandler, so you'd use it from your httpd.conf like this PerlModule My::TransHandler PerlTransHandler My::TransHandler and put your code, My/TransHandler.pm, someplace where mod_perl can see it, such as in ServerRoot/lib/perl/My/TransHandler.pm. see recipe 7.1 http://www.modperlcookbook.org/chapters/ch07.pdf for more details - it might help clear things up a bit. suburbanantihero states that the sections are only configurable on load time. typically, yes (as I also said :) but they will execute in .htaccess files as well (but don't worry about that, it's not what you are after). So I would need to bind it as a handler to the ssl virtualhost section. Is this correct? translation handlers run for every request and can be scoped on a virtual host basis. so, once it's installed it will do the mapping you require. I am not sure how this would then be invoked. Would it require further extension to my URI? the job of a translation handler is to map a URI to a filename on disk. in this case, you would be envoking a bit of trickery - altering the URI so that the default Apache translation engine thinks the URI is different than it really is. but as I just said, it will be run on every request - it is invoked by virtue of its nature, as a product of how Apache handles requests and allows you to plug into them. anyway, looks like you need to settle down with some mod_perl documentation and understand the Apache request cycle a bit :) http://perl.apache.org/ is the place to start. you also might find the general request cycle overview here http://www.modperlcookbook.org/chapters/part3.pdf helpful HTH --Geoff -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
perl module to access php_value include_path objects
I am in the middle of a project that requires me to dynamically update certain default paths within the Apache Server environment. I currently am able to update document_root on the fly and now need to be able to update php_value include_path in the same manor. Is there an existing perl module that will allow me to access this object dynamically per request? I have done some cursory search and have come up empty handed. Thank you for your assistance. Respectfully, Gary -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Request Object Work Flow - is_initial_req, is_main, main
I am very near in completing a module that allows one to dynamically re-map Apache's DocumentRoot directive based on a given URI. I've been able to get past several obstacles, but am having a very difficult time understanding the request object work flow. My problem seems to be due to subrequests not being mapped properly. The initial request seems to map as it should, but subrequests are randomly mapped or not mapped at all. I can reload the same page and get different subrequests to map, while the previously working subrequests no longer map. My only thought is that it is due to my lack of understanding of the request object work flow. Any basic pointers or examples that could give me a better understanding of this process would be greatly appreciated. Sincerely, Gary -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Re: Request Object Work Flow - is_initial_req, is_main, main
Geoffrey,
Once again, I appreciate your informative responses.
I've decided to abandon the idea in favor of using mod_rewrite.
I discovered the back reference capability in mod_rewrite and combined
with some php trickery have been able to produce the desired shared ssl
effect.
Thank you again for your wonderful assistance.
Respectfully,
Gary
Geoffrey Young wrote:
Gary C. New wrote:
I am very near in completing a module that allows one to dynamically
re-map Apache's DocumentRoot directive based on a given URI.
I've been able to get past several obstacles, but am having a very
difficult time understanding the request object work flow.
My problem seems to be due to subrequests not being mapped properly.
The initial request seems to map as it should, but subrequests are
randomly mapped or not mapped at all. I can reload the same page and
get different subrequests to map, while the previously working
subrequests no longer map.
this is a really difficult thing you are trying to do.
basically, DocumentRoot is a property of the server - if you modify it the
changes are propagated for all later requests to the same Apache child. so,
if you want to mess with it you need to be sure to set it back before the
next request starts.
so, say you have a request where you change the DocumentRoot and schedule a
cleanup to reset it. now, in the middle of that request you have a
subrequest. this subrequest probably thinks that the original DocumentRoot
is the one you just set in the main request, etc.
messing around with server attributes on a per-request level is tricky. in
general, I'd suggest against it - the only reason I've ever seen where it is
required to alter the DocumentRoot is for supporting FrontPage extensions.
other than that, there are ways around coding a dependency around
$ENV{DOCUMENT_ROOT}, such as coherent relative paths - it's is supposed to
be private to Apache core anyway :)
that said, you might be able to add some logic so that the the real
DocumentRoot is set in $r->notes via
$r->notes(?REAL_DOCROOT => $r->document_root) if $r->is_initial_req;
then for restoration everyone looks at $r->main->notes instead of relying on
what is in $r->document_root.
as an alternative, you could always just place the value you want for your
new DocumentRoot in notes from a fixup handler, then crack open
util_script.c in the apache 1.3 sources, and alter ap_add_common_vars to use
your notes value for DOCUMENT_ROOT instead of ap_document_root. something
like this (untested)
Index: src/main/util_script.c
===
RCS file: /home/cvspublic/apache-1.3/src/main/util_script.c,v
retrieving revision 1.168
diff -u -r1.168 util_script.c
--- src/main/util_script.c 1 Jan 2004 13:32:54 - 1.168
+++ src/main/util_script.c 11 Feb 2004 15:08:06 -
@@ -203,6 +203,7 @@
array_header *hdrs_arr = ap_table_elts(r->headers_in);
table_entry *hdrs = (table_entry *) hdrs_arr->elts;
int i;
+char *docroot;
/* use a temporary table which we'll overlap onto
* r->subprocess_env later
@@ -290,7 +291,10 @@
ap_table_addn(e, "REMOTE_HOST", host);
}
ap_table_addn(e, "REMOTE_ADDR", c->remote_ip);
-ap_table_addn(e, "DOCUMENT_ROOT", ap_document_root(r));/* Apache */
+if (! (docroot = ap_table_get(r->notes, "REAL_DOCROOT")) ) {
+docroot = ap_document_root(r);
+}
+ap_table_addn(e, "DOCUMENT_ROOT", docroot);/* Apache */
ap_table_addn(e, "SERVER_ADMIN", s->server_admin); /* Apache */
ap_table_addn(e, "SCRIPT_FILENAME", r->filename); /* Apache */
HTH
--Geoff
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Shared SSL Custom Log Parsing
I've got shared ssl setup with mod_rewrite and I am trying to figure out the best way to direct logging for each of the vhosts using the shared ssl connection and thought mod_perl might be good for this. My thinking is to setup a section in the httpd.conf file that watches the referrer environment variables as they come in for the shared ssl connection and then rewrite them to the appropriate custom vhost access/error logs. Referrer Variable: https://secure.provider.tld/secure/domain.tld/ Rewrite Logs: CustomLog /home/domain.tld/logs/access.log ErrorLog /home/domain.tld/logs/error.log or I noticed on the perl.apache.org site an example called "Logging to syslog" that could be used similarly but for the custom access/error logs. It pipes the general incoming logs to a program that then parses and rewrites the logs appropriately. I guess my main question with either example is what is the best way to write the parsed logs to these custom log files? Is there an existing module for this purpose? Is there a better way to parse and rewrite logs to custom files on-the-fly? Respectfully, Gary -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Re: Shared SSL Custom Log Parsing
I'm using a back reference to the http_referer with mod_rewrite to determine which vhost the shared ssl connection should be rewritten to. I know of no better solution for sharing an ssl connection. I would be open to suggestions. Respectfully, Gary Issac Goldstand wrote: You should know where they're coming from the same way you do in mod_rewrite. Besides that, referers can be spoofed, and I some clients don't even give you a referer... Issac - Original Message ----- From: "Gary C. New" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 25, 2004 12:19 PM Subject: Shared SSL Custom Log Parsing I've got shared ssl setup with mod_rewrite and I am trying to figure out the best way to direct logging for each of the vhosts using the shared ssl connection and thought mod_perl might be good for this. My thinking is to setup a section in the httpd.conf file that watches the referrer environment variables as they come in for the shared ssl connection and then rewrite them to the appropriate custom vhost access/error logs. Referrer Variable: https://secure.provider.tld/secure/domain.tld/ Rewrite Logs: CustomLog /home/domain.tld/logs/access.log ErrorLog /home/domain.tld/logs/error.log or I noticed on the perl.apache.org site an example called "Logging to syslog" that could be used similarly but for the custom access/error logs. It pipes the general incoming logs to a program that then parses and rewrites the logs appropriately. I guess my main question with either example is what is the best way to write the parsed logs to these custom log files? Is there an existing module for this purpose? Is there a better way to parse and rewrite logs to custom files on-the-fly? Respectfully, Gary -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Re: [OT] Shared SSL Custom Log Parsing
So how do you parse and rewrite these logs to appropriate log files? I need to be able to offer these ssl log entries to customers, too. It seems most logical to parse the ssl logs as they come in and then append them to the customers standard log files. Thank you for your input. Respectfully, Gary Issac Goldstand wrote: I do it by rewriting based on directory (https://secure.mydomain.com/shared/virtualdomain.com/index.html ) I figure there should be some incentive for people to get their own private SSL - also, users coming to a shared secure site have a better chance to realize that it's shared SSL and won't come complaining to ME if the virtualhost does something nasty to their credit card :) I'm using a back reference to the http_referer with mod_rewrite to determine which vhost the shared ssl connection should be rewritten to. I know of no better solution for sharing an ssl connection. I would be open to suggestions. Respectfully, Gary Issac Goldstand wrote: You should know where they're coming from the same way you do in mod_rewrite. Besides that, referers can be spoofed, and I some clients don't even give you a referer... Issac - Original Message - From: "Gary C. New" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 25, 2004 12:19 PM Subject: Shared SSL Custom Log Parsing I've got shared ssl setup with mod_rewrite and I am trying to figure out the best way to direct logging for each of the vhosts using the shared ssl connection and thought mod_perl might be good for this. My thinking is to setup a section in the httpd.conf file that watches the referrer environment variables as they come in for the shared ssl connection and then rewrite them to the appropriate custom vhost access/error logs. Referrer Variable: https://secure.provider.tld/secure/domain.tld/ Rewrite Logs: CustomLog /home/domain.tld/logs/access.log ErrorLog /home/domain.tld/logs/error.log or I noticed on the perl.apache.org site an example called "Logging to syslog" that could be used similarly but for the custom access/error logs. It pipes the general incoming logs to a program that then parses and rewrites the logs appropriately. I guess my main question with either example is what is the best way to write the parsed logs to these custom log files? Is there an existing module for this purpose? Is there a better way to parse and rewrite logs to custom files on-the-fly? Respectfully, Gary -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
[mp2] rflush.t Failed test
I am trying to build mp2 against apache 2.0.48 and perl 5.8.1-RC4. I am using the standard options to build: perl Makefile.PL \ MP_APXS=/usr/local/apache2/sbin/apxs \ MP_INST_APACHE2=1 Everything seems to compile fine, but when I run make test the rflush.t test fails and I cannot figure out what is causing it. t/api/rflush# Failed test 1 in t/api/rflush.t at line 13 t/api/rflushFAILED test 1 Failed 1/1 tests, 0.00% okay I checked the error_log and it does not seem to provide any critical information regarding this issue. Suggestions? Respectfully, Gary -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Re: [mp2] rflush.t Failed test
The version of perl I am using is the latest Mandrake binary. -8<-- Start Bug Report 8<-- 1. Problem Description: [DESCRIBE THE PROBLEM HERE] 2. Used Components and their Configuration: *** mod_perl version 1.9913 *** using lib/Apache/BuildConfig.pm *** Makefile.PL options: MP_APXS => /usr/local/apache2/sbin/apxs MP_COMPAT_1X=> 1 MP_GENERATE_XS => 1 MP_INST_APACHE2 => 1 MP_LIBNAME => mod_perl MP_USE_DSO => 1 MP_USE_STATIC => 1 *** /usr/local/apache2/sbin/httpd -V Server version: Apache/2.0.48 Server built: Mar 25 2004 22:45:12 Server's Module Magic Number: 20020903:4 Architecture: 32-bit Server compiled with -D APACHE_MPM_DIR="server/mpm/worker" -D APR_HAS_SENDFILE -D APR_HAS_MMAP -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled) -D APR_USE_SYSVSEM_SERIALIZE -D APR_USE_PTHREAD_SERIALIZE -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT -D APR_HAS_OTHER_CHILD -D AP_HAVE_RELIABLE_PIPED_LOGS -D HTTPD_ROOT="/usr/local/apache2" -D SUEXEC_BIN="/usr/local/apache2/bin/suexec" -D DEFAULT_SCOREBOARD="logs/apache_runtime_status" -D DEFAULT_ERRORLOG="logs/error_log" -D AP_TYPES_CONFIG_FILE="/etc/apache2/conf/mime.types" -D SERVER_CONFIG_FILE="/etc/apache2/conf/httpd.conf" *** /usr/bin/perl -V Summary of my perl5 (revision 5.0 version 8 subversion 1) configuration: Platform: osname=linux, osvers=2.4.18-23mdksmp, archname=i386-linux-thread-multi uname='linux hp6.mandrakesoft.com 2.4.18-23mdksmp #1 smp fri aug 2 12:31:40 cest 2002 i686 unknown unknown gnulinux ' config_args='-des -Dinc_version_list=5.8.0/i386-linux-thread-multi 5.8.0 5.6.1 5.6.0 -Darchname=i386-linux -Dcc=gcc -Doptimize=-O2 -fomit-frame-pointer -pipe -march=i586 -mcpu=pentiumpro -Dprefix=/usr -Dvendorprefix=/usr -Dsiteprefix=/usr -Dman3ext=3pm -Dcf_by=MandrakeSoft -Dmyhostname=localhost [EMAIL PROTECTED] -Dd_dosuid -Ud_csh -Duseshrplib -Dusethreads' hint=recommended, useposix=true, d_sigaction=define usethreads=define use5005threads=undef useithreads=define usemultiplicity=define useperlio=define d_sfio=undef uselargefiles=define usesocks=undef use64bitint=undef use64bitall=undef uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='gcc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm', optimize='-O2 -fomit-frame-pointer -pipe -march=i586 -mcpu=pentiumpro ', cppflags='-D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -fno-strict-aliasing -I/usr/local/include -I/usr/include/gdbm' ccversion='', gccversion='3.3.1 (Mandrake Linux 9.2 3.3.1-1mdk)', gccosandvers='' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8 alignbytes=4, prototype=define Linker and Libraries: ld='gcc', ldflags =' -L/usr/local/lib' libpth=/usr/local/lib /lib /usr/lib libs=-lnsl -lndbm -lgdbm -ldl -lm -lcrypt -lutil -lpthread -lc perllibs=-lnsl -ldl -lm -lcrypt -lutil -lpthread -lc libc=/lib/libc-2.3.2.so, so=so, useshrplib=true, libperl=libperl.so gnulibc_version='2.3.2' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-rdynamic -Wl,-rpath,/usr/lib/perl5/5.8.1/i386-linux-thread-multi/CORE' cccdlflags='-fPIC', lddlflags='-shared -L/usr/local/lib' Characteristics of this binary (from libperl): Compile-time options: MULTIPLICITY USE_ITHREADS USE_LARGE_FILES PERL_IMPLICIT_CONTEXT Locally applied patches: RC4 Built under linux Compiled at Sep 1 2003 17:29:01 %ENV: PERL_LWP_USE_HTTP_10="1" @INC: /usr/lib/perl5/5.8.1/i386-linux-thread-multi /usr/lib/perl5/5.8.1 /usr/lib/perl5/site_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.1 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.1 /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl . *** Packages of interest status: Apache::Request: - CGI: 3.04 LWP: 5.69 mod_perl : - 3. This is the core dump trace: (if you get a core dump): [CORE TRACE COMES HERE] This report was generated by t/REPORT on Tue Apr 6 22:00:29 2004 GMT. ---------8<-- End Bug Report --8<-- It looks like Mandrake is still using 1.9909 with the current build. I'll see if I can find a spec file and see what they had to do do build it. I appreciate
Re: [mp2] rflush.t Failed test
I found the Mandrake source rpm spec file and have tried to build mod_perl-1.99_09 from source using it as a guide. It seems that there is not a rflush.t test in the mod_perl-1.99_09 distribution; thus, rendering any help from the spec file useless. Is there an older version of mod_perl-1.99 that builds well against perl-5.8.1? Respectfully, Gary Geoffrey Young wrote: Gary C. New wrote: I am trying to build mp2 against apache 2.0.48 and perl 5.8.1-RC4. hi I'm not sure about the differences between RC4 and 5.8.2, but I'd suggest using an official version (5.8.2, 5.8.3, etc) and report back with the gory details listed here: http://perl.apache.org/docs/2.0/user/help/help.html#Important_Information thanks --Geoff -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
[mp2] rflush failed test w/ Mandrake 9.2
Stas, You may have seen my post on the mod_perl list about rflush failed test with MP2. I'm using Mandrake 9.2 and I heard that you use Mandrake with your mod_perl install. Could you give me a brief synopsis of your mod_perl-2.0 setup on Mandrake? I'm trying to build MP2 against Mandrake's stock perl-5.8.1 rpm and my own custom Apache2. Everything seems to complete fine except the rflush test fails every time. This is the ONLY test that fails. I've tried updating against MODPERL_1_99_13 and HEAD with no success. 5005threads are undefined and ithreads are defined with the stock perl rpm. The rflush test seems to fail at the very last line when it tries to compare the expected and received variables. Is there any way to check these variables' output? I would appreciate any suggestions you may have. Respectfully, Gary -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Re: [mp2] rflush failed test w/ Mandrake 9.2
I upgraded from Mandrake's stock 9.2 perl rpms to the stock 10.0 perl rpms (perl-5.8.3-5mdk) and it works like a charm. The perl upgrade wasn't as painful as I thought it might be. I upgraded perl, perl-base, and perl-devel and the only dependence I had to worry about was mandrake-doc-common. I appreciate everyones advice. Consider this issue resolved. Respectfully, Gary Stas Bekman wrote: Hi Gary, You may have seen my post on the mod_perl list about rflush failed test with MP2. Wasn't it resolved already? I thought you reported success. I'm using Mandrake 9.2 and I heard that you use Mandrake with your mod_perl install. Could you give me a brief synopsis of your mod_perl-2.0 setup on Mandrake? I'm trying to build MP2 against Mandrake's stock perl-5.8.1 rpm and my I remember seeing 5.8.1 RC4, right? You really need to have a release version and not a development one. RC is not good. The fact that the distro decides that it's good for their own needs, doesn't necessarily mean it's good for the rest of the projects. I suggest that you either move to a higher version or build your own. own custom Apache2. Everything seems to complete fine except the rflush test fails every time. This is the ONLY test that fails. I've tried updating against MODPERL_1_99_13 and HEAD with no success. 5005threads are undefined and ithreads are defined with the stock perl rpm. The rflush test seems to fail at the very last line when it tries to compare the expected and received variables. Is there any way to check these variables' output? Certainly, just run it in the verbose mode: t/TEST -v api/rflush and post it here. Please repost the whole bugreport info, as I don't have it around. I would appreciate any suggestions you may have. Let's see what the verbose output gives first. FWIW, I don't use stock Mandrake perl for testing and in any case I'm running Mandrake 10 with perl-5.8.3-5mdk, so it won't help you much. I can post my custom build of perl 5.8.1's info (but this is *not* RC4) after you tell me which one do you use, in the bugreport. There are so many ways to build perl. __ Stas BekmanJAm_pH --> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
