about your setup.
__
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
/ so we know more about your setup.
__
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
to improve things are always welcome.
__
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
FYI
Original Message
Date: Fri, 19 Sep 2003 10:44:13 +0800
From: Autrijus Tang [EMAIL PROTECTED]
To: John Peacock [EMAIL PROTECTED]
CC: Perl 5 Porters [EMAIL PROTECTED]
??, 2003-09-19 00:05, John Peacock
What is the status of thread support on FreeBSD vis-a-vis Perl? There is
Matisse Enzer wrote:
At 11:19 AM -0700 9/19/03, Stas Bekman wrote:
Matisse Enzer wrote:
Thank you very much.
So does it work now?
I wasn't able to get 1.99_09 to install.
-8-- Start Bug Report 8--
1. Problem Description:
make install
.
__
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
has fixed that, check the Changes file.
t/response/TestApache/conftree.pm does the testing of this feature and works
just fine in the current cvs.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org
to point people to a simple:
http://perl.apache.org/bugs/
Thanks.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto:[EMAIL PROTECTED] http
with
modperl. There are many other appropriate places where you can ask this
question. See: http://perl.apache.org/docs/offsite/other.html
Let's keep the Signal to Noise ratio high on this list. Thank you.
__
Stas BekmanJAm_pH
#Porting_CPAN_modules_to_mod_perl_2_0_Status
thanks.
__
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
.
__
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
a non-issue as well ;)
__
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
MODPERL_AP_LIBEXECDIR to
MODPERL_AP_MODDIR since it specifies where Apache's modules directory
is and there isn't a libexec anymore?
It's the problem with apxs then, since mp2 just uses the same names as apxs:
~/httpd/prefork/bin/apxs -q LIBEXECDIR
/home/stas/httpd/prefork/modules
~/httpd/prefork
will later read them in archives.
Thank you!
__
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
PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto:[EMAIL PROTECTED] http
someone would like to summarize these and put a short tutorial on
perl.apache.org? This question seems to come back pretty often.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide
FYI: Free DNS for the Perl Community
http://www.dyndns.org/news/releases/archives/2002/09/74.html
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
will be installed into MP_AP_PREFIX/lib
# for use by 3rd party xs modules
$self-{cwd}/src/modules/perl/$self-{MP_LIBNAME}.lib;
}
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide
Randy Kobes wrote:
On Fri, 12 Sep 2003, Stas Bekman wrote:
Steve Hay wrote:
Stas Bekman wrote:
Randy Kobes wrote:
On Fri, 12 Sep 2003, Steve Hay wrote:
I believe that mod_perl 2 now installs the mod_perl.lib
somewhere to solve that kind of problem. Is there an
option in the mod_perl 1 build
cycles, first upgrade to the latest mod_perl:
http://perl.apache.org/download/index.html
and try again.
Thanks.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http
the current modperl-2.0 cvs to get this functionality.
Please report any problems that you may have noticed.
So here is how the new log will look:
/home/stas/apache.org/portland3 t/SMOKE -bug_mode
running t/TEST in the bug report mode
apache/add_configok
apache/cgihandler
I think I got your problem solved, you need to:
- print $q-header();
+ print $q-header(text/html; charset=utf-8);
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http
[Forwarded from [EMAIL PROTECTED] [EMAIL PROTECTED]]
Hello,
In response to :
Kurt George Gjerde wrote:
BTW: I've fixed my can't coerce GLOB to string problem I had last
week.
Was unrelated to mod_perl (sorry). It seems XML::LibXSLT produced some
errors which went straight to STDERR. Under
list of modules...
__
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
Bart Terryn wrote:
Stas and all of the others,
Stas said:
I think I got your problem solved, you need to:
- print $q-header();
+ print $q-header(text/html; charset=utf-8);
Well actually you did not.
Probably you looked a bit too fast.
(forgivable in view of the numbers of mails you reply
to use the latest released
mod_perl 1.99_09 and apache 2.0.47 before you start reporting problems which
were fixed alredy. You can find rawhide rpm versions of those on rpmfind.net.
__
Stas BekmanJAm_pH -- Just
__
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
community for mod_perl, it has made
the development of this project fun! And it has kept me from having to
go back to C programming. It was a long time since I last did that.
thanks for the kind words ;)
__
Stas BekmanJAm_pH
is what raised the interest of a few mod_perl
developers. However, at the moment, there is nothing new here.
Nigel
[EMAIL PROTECTED]
--
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org
Philip M. Gollucci wrote:
Stas Wrote:
I believe it's not the problem Bart was talking about. You are most
likely talking about Apache-request failing, which is how it should be
if the GlobalRequest option is not set. Bart's problem was finding
the request method.
If you'll read carefully
speeves wrote:
Stas Bekman wrote:
Thanks that did it.
Great.
It would be nice though if the minimum rev level of the CGI.pm could be
mentioned in the doc.
Or maybe it is there somewhere and I skimmed over it.
It's a a CGI.pm problem, really. We can't go and support all possible
modules
/authors/id/L/LD/LDS/
__
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
.
Thanks.
__
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
, I have updated the page.
__
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
/ModPerl-Registry/t/cgi-bin/r_in
herited.pl
What perms do you get when you do:
ls -l ModPerl-Registry/t/cgi-bin/r_inherited.pl
it should be a+rx, e.g. on my machine it's:
-rwxr-xr-x1 stas stas 248 Mar 7 19:58
I think when I have added this file to cvs it didn't have the +x bit, which
Beau E. Cox wrote:
May be you have an old checkout of this file, try to do:
rm ModPerl-Registry/t/cgi-bin/r_inherited.pl
cvs up ModPerl-Registry/t/cgi-bin/r_inherited.pl
and try again.
Thanks Stas -
Sorry I missed the error. I did the 'rm' and re-cvs'ed -
flags correct and test OK. Next I
.
__
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
.
__
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
object method request via package Apache at C:/Perl/lib/CGI.pm line
269.
upgrade your CGI.pm to 2.93 or higher.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http
/cgihandler.t
t/response/TestApache/cgihandler.pm
t/modules/cgi.t
t/response/TestModules/cgi.pm
t/modules/cgiupload.t
t/response/TestModules/cgiupload.pm
of course you will want to create a new couple of files for this test.
__
Stas
-5.8.1 snapshot, while you are at it,
as it'll be released rsn.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto:[EMAIL PROTECTED] http
. Please check if it works for you.
I've already adjusted the install docs to mention MP_APXS, I suppose we need
to put it as the very first one.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org
a few knowledgeable
folks over there...
Next I am going to try perl 5.8.1 snapshot to see what happens.
Probably nothing will change on the sharing front, but you will get a better
perl ;)
__
Stas BekmanJAm_pH
] [error] 1688: ModPerl::Registry: Can't locate
object method request via package Apache at C:/Perl/lib/CGI.pm line 269.
upgrade your CGI.pm to 2.93 or higher.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http
it there.
__
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
will know the rest
of
the details about the layout. Please check if it works for you.
I've already adjusted the install docs to mention MP_APXS, I suppose we
need
to put it as the very first one.
Yep - MP_APXS=... works, thanks Stas.
I have updated the install docs to reflect the ever-changing reality
being a bonehead? Thank you in advance for any
assistance.
Compare their build options?
perl-5.6.1 -V 5.6.1
perl-5.8.0 -V 5.8.0
diff -u 5.6.1 5.8.0
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http
a request to a registry script?
I suppose nothing? There is no segfault, no nothing? What's the exact error
message that you get from the system? (I suppose it does that via a pop up
window, right?)
__
Stas BekmanJAm_pH
(assuming that you are using the latest cvs):
perl -MApache2 -MAPR -MAPR::UUID -le 'print APR::UUID-new-format'
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http
://perl.apache.org/bugs/
__
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
John Saylor wrote:
hi
( 03.09.03 10:42 -0700 ) Stas Bekman:
You mean, you want to generate one? in mod_perl2/apr it'd be:
is there an equivalent in mod_perl1?
I'm sure there are a few modules on CPAN that you can use. Again I'm talking
about generating UUD, not extracting the SSL one. Perrin
the same script work fine as mod_cgi?
__
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
/A'
__
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
--
Reporting bugs
Stas had suggested that either IPC::Run or Apache::SubProcess could be
used.
I have 2 versions of a mod_perl script using either of the modules. Which
one would be preferred and why?
Some reasons come to mind right away, e.g.,
* IPC::Run may be more mature (version 0.75), so use it.
Don't
/
__
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
--
Reporting
to under, which is
probably not what you want.
- for users of perl 5.6 suggest to use 'use vars' instead of 'our'.
- point to perl_reference.pod for other workarounds/solutions.
Does it sound good?
__
Stas BekmanJAm_pH
$counter exapmle.
Thanks!
__
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
: *** [run_tests] Error 1
[EMAIL PROTECTED]:~/.cpan/build/Apache-Test-1.03#
--
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto:[EMAIL PROTECTED
it to the perl reference section.
__
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
request
* @return A fully qualified URL
* @deffunc char *ap_construct_url(apr_pool_t *p, const char *uri,
request_rec *r)
*/
AP_DECLARE(char *) ap_construct_url(apr_pool_t *p, const char *uri,
request_rec *r);
__
Stas Bekman
Tofu Optimist wrote:
Thanks. How do I call construct_uri?
You just call $r-construct_url. In your example that would be:
$r-headers_out-set(Location = $r-construct_url . r2=1);
__
Stas BekmanJAm_pH -- Just
example
that would be:
$r-headers_out-set(Location =
$r-construct_url . r2=1);
__
Stas BekmanJAm_pH -- Just Another
mod_perl Hacker
http://stason.org/ mod_perl Guide ---
http://perl.apache.org
mailto:[EMAIL PROTECTED
to do that, even though there are claims that short
writes are atomic. It's probably not the same on all io implementations.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide
[EMAIL PROTECTED] wrote:
In private mail Stas Bekman [EMAIL PROTECTED] writes:
oops, that should be the modperl list... at modperl-docs we discuss
mostly site/docs techical issues and there are very few people on this
list to get enough exposure for this kind of feedback request.
Patch
is that the initial read pipe apparently fails to open
under modperl.
Is there a workaround for this? or am I just missing something
simple?
Use IPC::Run?
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http
a bug in Apache 1.3.28:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22805
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto:[EMAIL PROTECTED
on CPAN, and not release manager's one.
__
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
.
__
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
--
Reporting bugs: http
#C_Apache_E_gt_request_
__
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
messages or explaining what kind of problem he has.
On Fri, 29 Aug 2003 10:17:57 -0700, Stas Bekman [EMAIL PROTECTED] wrote:
Igor Ivoilov wrote:
Hello all,
I have perl programs running under Apache::Registry.
Now I need to switch to mod_perl2 and can not find request object.
I used to get as
$r
.
__
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
much better to die with a
useful hint on how to tell where APXS is.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto:[EMAIL PROTECTED] http
I'm about to release a new GTop (you need it for Apache::VMonitor), please
give it a try http://apache.org/~stas/GTop-0.11.tar.gz and report any problems
to me (off list). Thanks.
Changes since 0.10:
Add support to libgtop 2.0 and automate the picking of the right libraries
and include paths
-debugging information
inserted. Make sure that you load before any code that you plan to profile.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
__
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
--
Reporting bugs
if you can share your solution, I'd it to that section.
__
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
/TEST -v filter/in_bbs_msg.t hooks/trans.t
don't run 'make test' as it'll rewrite t/conf/httpd.conf, use t/TEST instead.
I wonder why http://httpd.apache.org/docs-2.0/mod/core.html#enablesendfile
says that it's on by default.
__
Stas
.
__
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
do any additions/fixes there, you will need to use the modperl-2.0 cvs
repository, available from here:
http://perl.apache.org/download/source.html#Development_mod_perl_2_0_Source_Distribution
and What would be most
appropriate: post patches and questions here, to Stas directly, or
somewhere
('LIBEXECDIR'),
+ $self-apxs('LIBEXECDIR').'-extramodules',
catfile($sroot, 'modules'),
catfile($sroot, 'libexec'));
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org
off
any autoresponders that you may have. :(
__
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
a list signature:
Always post followups back to the list!
will help, but who reads that.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto
#Development_mod_perl_2_0_Source_Distribution
(note: I have just committed the test, so if you use the snapshot, which is
updated every 6 hours, it may not be there, so use the normal cvs checkout)
__
Stas BekmanJAm_pH -- Just
Larry Leszczynski wrote:
On Tue, 26 Aug 2003, Stas Bekman wrote:
Please advise on another way to tell people to respond to the list and not in
private. I used to receive much less off-list replies earlier.
[snip]
Purhaps adding a list signature:
Always post followups back to the list
Douglas Theobald wrote:
I thought this was a strange behavior for the list messages when I realized
that I had replied, accidentally, to Stas personally and not the list. I
subscribe to six lists, and mod_perl is the *only* one where my email reader
automatically replies to the sender
to the functions. http://perl.apache.org/bugs/
provides the details on how to do that.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto:[EMAIL PROTECTED
bugs properly in the future.
Alan, as Ged suggested, upgrade your perl to 5.6.1 or 5.8.0 (5.8.1 was not
released yet) and try again (you will need to rebuild mod_perl once you did that).
__
Stas BekmanJAm_pH -- Just
: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
--
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
Udo Rader wrote:
Am Tue, 26 Aug 2003 16:07:21 + schrieb Stas Bekman:
As you posted in the followup, this is a problem with all Apache:: modules.
The problem originates within Apache, not us.
Didn't know that apache rejects to run as root. Strange (but safe) behaviour.
It starts as root
/?
__
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
.
__
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
Geoffrey Young wrote:
Stas Bekman wrote:
Craig Shelley wrote:
I'll take a look at it. But you didn't supply a complete bug report
as explained http://perl.apache.org/bugs/. Please do so.
I think I've got this figured out.
the problem is with the r-main logic in mpxs_ap_run_sub_req
from the filter handler.
I have somewhere a prototype for the new API which tells what phase we are in,
but it's possible that there is a more efficient way to tell the difference.
__
Stas BekmanJAm_pH -- Just Another
to flush any data before
issuing a subrequest? If I remember correctly you aren't.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto:[EMAIL
by the apache user, or build/run the tests as a non-root.
If you configure your CPAN to put the build dir not under /root, but let's say
/tmp/ (probably can come up with a better choice), it'll work.
__
Stas BekmanJAm_pH
:
[...]
3. This is the core dump trace: (if you get a core dump):
[CORE TRACE COMES HERE]
Thanks, but you have missed the core dump's backtrace.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org
[EMAIL PROTECTED] wrote:
On Tue, 26 Aug 2003 09:07:21 -0700, Stas Bekman wrote:
[snip]
As you posted in the followup, this is a problem with
all Apache:: modules.
The problem originates within Apache, not us.
FWIW, the cvs version of Apache::Test warns you early
whether this is going to
work
are trying to run mod_perl 1.0 modules with mod_perl 2.0. In
order to help us to help you, you must always submit a complete bug report as
explained here: http://perl.apache.org/bugs/
__
Stas BekmanJAm_pH -- Just
Craig Shelley wrote:
On Tue, 2003-08-26 at 19:03, Stas Bekman wrote:
Thanks, but you have missed the core dump's backtrace.
I am sorry but I have never used core files before, so forgive me if I
have done this all wrong.
No worries, this task is not trivial. Your trace is almost perfect
the exact information we need to help them.
__
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
1 - 100 of 2823 matches
Mail list logo
