The Bricolage development team is pleased to announce the release of
Bricolage 1.8.5. This maintenance release addresses a number of
issues in
Bricolage 1.8.3 and adds a number of improvements (there was no
announcement for the short-lived 1.8.4 release). The SOAP server in
par
Barry Hoggard wrote:
On Mar 18, 2005, at 5:25 PM, Stas Bekman wrote:
Barry Hoggard wrote:
On Mar 14, 2005, at 7:38 PM, Barry Hoggard wrote:
What is the best way to do the MyError example from the Eagle book
in MP2? If I get an uncaught error, and I have something like this
set up:
ErrorDocu
On Fri, 2005-03-18 at 03:15 -0600, D. Hageman wrote:
> On Thu, 17 Mar 2005, Stas Bekman wrote:
>
> > James Orr wrote:
> >> Hi,
> >>
> >> I have an occaisional error happening with a module i'm using from a
> >> mod_perl script. This is in my "new" method ...
> >>
> >> my $ifh = IO::File->new($p
On Mar 18, 2005, at 5:25 PM, Stas Bekman wrote:
Barry Hoggard wrote:
On Mar 14, 2005, at 7:38 PM, Barry Hoggard wrote:
What is the best way to do the MyError example from the Eagle book
in MP2? If I get an uncaught error, and I have something like this
set up:
ErrorDocument 500 /error
Anders, the first priority is to figure out how to reproduce the problem
at will. If you don't manage that, you most likely are going to waste
hours staring at the screen. I'd concentrate on that task first.
Try using ab (apachebench), httpd_load or another utility to stress test.
More advanced
On Fri, 2005-03-18 at 11:15 -0500, Stas Bekman wrote:
> Anders, do you by chance use a proxy that may have eaten the response?
>
> What do you see in logs/access_log, it tells how many bytes were sent to
> the client.
>
> What happens if you replace print($x) with Apache->request->print($x)
>
Barry Hoggard wrote:
On Mar 14, 2005, at 7:38 PM, Barry Hoggard wrote:
What is the best way to do the MyError example from the Eagle book in
MP2? If I get an uncaught error, and I have something like this set up:
ErrorDocument 500 /error
SetHandler perl-script
PerlRespon
The uploaded file
Apache-VMonitor-2.03.tar.gz
has entered CPAN as
file: $CPAN/authors/id/S/ST/STAS/Apache-VMonitor-2.03.tar.gz
size: 22407 bytes
md5: 39b23f06c00e59cda6b66bb166e1cfd1
Changes since 2.02:
use %Apache::VMonitor::longflags long status lookup table, using the
values returned
The uploaded file
Apache-Scoreboard-2.06.tar.gz
has entered CPAN as
file: $CPAN/authors/id/S/ST/STAS/Apache-Scoreboard-2.06.tar.gz
size: 18383 bytes
md5: 06b4f22250d954b8a6bd607884ad09b3
You want this module only if you use mod_perl 2!
Changes since 2.05:
fix the buggy reconstruction of
The uploaded file
Apache-Scoreboard-0.15.tar.gz
has entered CPAN as
file: $CPAN/authors/id/S/ST/STAS/Apache-Scoreboard-0.15.tar.gz
size: 12014 bytes
md5: 688e6650c102da6a54dc5b0df6d21bb6
You want this module only if you use mod_perl 1!
Changes since 0.14:
use PERL_NO_GET_CONTEXT macro to
After posting on the libaprq list i learned this:
"libaprq has the file permissions hardcoded to 0600 and ignores the
user's umask"
chmod is in order.
On Mar 18, 2005, at 12:20 AM, jonathan vanasco wrote:
Just setting a simple umask did do the trick for 90% of my needs
I'm stuck on one issue th
On Mar 14, 2005, at 7:38 PM, Barry Hoggard wrote:
What is the best way to do the MyError example from the Eagle book in
MP2? If I get an uncaught error, and I have something like this set
up:
ErrorDocument 500 /error
SetHandler perl-script
PerlResponseHandler MyError
On Mar 18, 2005, at 9:02 AM, Mike Whitaker wrote:
Getting an error from mod_per/Apache2 as soon as I try and access an
protected page:
'failed to resolve handler Foo::Auth'
I'm assuming this means something more than 'can't find Foo::Auth in
@INC', since another Foo:: module (in use as an Output
Dominique Quatravaux wrote:
I wrote:
Stop the press! My patch was incomplete:
... and this one was incomplete too, I forgot about the POD. It looks
like I am doomed to make a fool of myself in every conceivable way on
this list :-( Apologies yet again.
[...]
That's cool, it wasn't committed yet :
Nick *** wrote:
>Nick *** wrote:
>[...]
>> But there is another bug as I said.
>> Just run perl Makefile.PL MP_STATIC_EXTS=1 MP_COMPAT_1X=0 MP_USE_STATIC=1
MP_AP_CONFIGURE="--with-mpm=prefork" MP_AP_PREFIX=/usr/src/httpd
>> and then run make. You will see what happens :)
[...]
[EMAIL PROTECTE
Anders Nielsen wrote:
On Wed, 2005-03-16 at 21:11 -0500, Stas Bekman wrote:
Please see:
21.7. Hanging Processes: Detection and Diagnostics
http://modperlbook.org/html/ch21_07.html
Thank you for the reply.
The problem I described happened again and I was able to get some more
information.
The serve
> Error::TryCatch looks like a nice drop in replacement for Error.pm.
>
> This is the first time I've come across a source filter - looks like a
> really cool technique.
Hmmm - let me take that back. There are too many issues with parsing at
the moment.
So the construct :
$abc->new( PARAM => {
On Fri, Mar 18, 2005 at 09:10:11AM +, Andrew Green wrote:
> I fear that the fact that the problem is really very intermittent might
> hamper this, however. I should also probably have pointed out that
> there's a PostReadRequestHandler and a TransHandler in the config as
> well, which I gue
On Wed, 2005-03-16 at 21:11 -0500, Stas Bekman wrote:
> Please see:
> 21.7. Hanging Processes: Detection and Diagnostics
> http://modperlbook.org/html/ch21_07.html
>
Thank you for the reply.
The problem I described happened again and I was able to get some more
information.
The server isn't act
I wrote:
> Stop the press! My patch was incomplete:
... and this one was incomplete too, I forgot about the POD. It looks
like I am doomed to make a fool of myself in every conceivable way on
this list :-( Apologies yet again.
Index: ModPerl-Registry/lib/ModPerl/PerlRun.pm
==
On Tue, Mar 15, 2005 at 05:31:28PM -0500, Perrin Harkins wrote:
> BerkeleyDB, MySQL, or SQLite3, but I don't think BDB works in Win32.
Please don't tell my code that :). It's been using the BerkeleyDB module
on a daily basis for nearly a year with few problems. The module is
available as a PPM on
I wrote:
>The other problem is that I cannot Do The Right Thing while keeping
>the current API intact. I propose the attached patch as an alternative,
Stop the press! My patch was incomplete: I forgot to rename
"rewrite_shebang()" into "shebang_to_perl()" in subclasses
ModPerl::Registry and ModPe
Getting an error from mod_per/Apache2 as soon as I try and access an
protected page:
'failed to resolve handler Foo::Auth'
I'm assuming this means something more than 'can't find Foo::Auth in
@INC', since another Foo:: module (in use as an OutputFilter) gets
picked up fine.
WHat'm I missing?
c
OpenInteract 1.99_06 (2.0 beta 6) has been released to CPAN.
OpenInteract is a full-featured application server with
authentication, security, database access, content generation and lots
of other bells and whistles under one roof.
This release has lots of new features, improvements and bugfixes,
On Thu, 2005-03-17 at 15:19 -0500, Perrin Harkins wrote:
> > Is this still the feeling?
>
> Yes. Look at either Error::TryCatch (source filter) or
> Exception::Class::TryCatch (safe, but less magical).
Error::TryCatch looks like a nice drop in replacement for Error.pm.
This is the first time I'
>Nick *** wrote:
>[...]
>> But there is another bug as I said.
>> Just run perl Makefile.PL MP_STATIC_EXTS=1 MP_COMPAT_1X=0 MP_USE_STATIC=1
>> MP_AP_CONFIGURE="--with-mpm=prefork" MP_AP_PREFIX=/usr/src/httpd
>> and then run make. You will see what happens :)
>
>Indeed, I can reproduce it.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Geoffrey Young wrote:
| just added to svn is $ENV{MOD_PERL_API_VERSION}, which is currently
| just "2".
|
| I guess I understand why it's somewhat inconvenient sometimes to
| rely on %ENV, as with the system() example, but I'm not so sure
| that %ENV is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[...]
|
| *** Packages of interest status:
|
| Apache::Request: -
| CGI: 2.89
| LWP: 5.65
| mod_perl : 1.9907, 1.999021
That doesn't look good. You had already installed a previous version of
mod-perl namely 1.9907(very anc
On Thu, 17 Mar 2005, Stas Bekman wrote:
James Orr wrote:
Hi,
I have an occaisional error happening with a module i'm using from a
mod_perl script. This is in my "new" method ...
my $ifh = IO::File->new($project_dir.'/info.xml') || die "Can't open
info file: $!";
$data->{'info'} = $parser->parse_fh
On Thu, 17 Mar 2005 20:00:34 -0500, Stas Bekman wrote:
> Andrew, any chance you could minimise the script so that you can
> still reproduce the problem...
Many thanks for responding, Stas. I'll certainly try.
I fear that the fact that the problem is really very intermittent might
hamper this,
-8<-- Start Bug Report 8<--
1. Problem Description:
I had a mod_perl 1.x installed first on my apache2.x,now i have just
lear this configuration doestn,t work so i have installed mod_perl 2.x
from your sit and follow the steps.But the test is not giving OK.
31 matches
Mail list logo