On May 13, 2025, at 8:23 PM, Vincent Veyron wrote:
> Is there a way I could do :
>
> $r->print('Building tar file') ;
>
> every second or other until the tar file is built? I can't seem to think of
> one.
>
> My handler calls an sql script that dumps the database with system() :
>
>
On Dec 19, 2024, at 5:10 PM, Mithun Bhattacharya wrote:
> Has DBI itself become thread safe or is it still a great area ?
AFAIK, as long as each thread instantiates it's own handle, it should work. I
don't believe you can share the same DBI handle between multiple threads.
Regards,
Ed
On Dec 19, 2024, at 12:47 PM, Bitfox wrote:
> Mod_perl doesn’t support threads, am I right?
If you mean mod_perl with ithreads and using the Apache mpm_event module, then
that's incorrect, I think. Search the archives of this mailing list for posts
by Joe Schaefer for some clues as to how. I h
On Aug 6, 2024, at 7:59 PM, Vincent Veyron wrote:
> Not sure if it's Apache or mod_perl related, but I thought I'd mention it.
I would call that an Apache (mis)configuration issue, frankly. I don't think it
has anything to do with mod_perl specifically.
Certainly, it's a good thing to warn peop
On May 13, 2024, at 11:00 PM, Steven Haigh via modperl
wrote:
> If I was to guess, it seems like an interaction with open3 and modperl.
>
> https://perldoc.perl.org/IPC::Open3
Yes, this is a known problem with IPC::Open3 that is commonly seen with
mod_perl. It's been a Perl bug since 2009, and
On Feb 14, 2024, at 2:27 PM, Joe Schaefer wrote:
> sealed.pm is really only necessary in a mod_perl context. And really it only
> matters if you are using subrequests to reenter :Sealed handlers. Otherwise
> I don't see the point of the exercise.
Well, I suppose one point of the exercise would
On Feb 14, 2024, at 12:18 PM, Joe Schaefer wrote:
> pad.c will segfault with an out-of-bounds memory access at line 2460 of pad.c.
Is there a Perl/perl5 GitHub issue or pull request for this?
Regards,
Ed
Who do we need to beg or plead with to get a proper release of libapreq 2.18?
This has been an issue for over a year!
On Jan 11, 2024, at 4:00 AM, Randolf Richardson wrote:
> Thank you, Joe. Upgrading from libapreq-2.17 (via apt) to
> libapreq-2.18 (via svn) resolved my problem -- everyt
On Nov 15, 2023, at 7:43 PM, vv.lists wrote:
> I'm wondering if any of you has an idea of what caused this change in
> behaviour?
What versions were you using before you upgraded?
I would recommend comparing the differences between the versions. Start with
the change logs and then diff the so
