offer any suggestions as to how to get my
signal handler, PIPE, executed as soon as the SIGPIPE is generated?
Thanks
Jim Albert
--
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
Stas Bekman wrote:
Jim Albert wrote:
I'm trying to determine how to have my mod_perl apache server properly
catch a SIGPIPE signal in a timely manner.
My environment is Apache/2.0.49 (Fedora) and mod_perl 2.
Jim, please *always* report bugs and problems following these guidelines!
::SIG2
where Apache::SIG2.pm is defined in this example as:
--
package Apache::SIG2;
# This package adapted by Jim Albert from the original mod_perl1
# Apache::SIG.pm by Doug MacEachern and Doug Bagley
# This PerlHandler can be used to prevent httpd children from killing
# off non-mod-perled
}
sub sigCHLD_handler {
while (my $reaperpid = waitpid(-1,WNOHANG)>0) {
}
}
## do your while (1) and fork etc...
I wish I could paste in my whole daemon thing, but it is too far along with to many things specific to my bosses application..
Thanks,
Eric
At 02:55
blacklist.
relay=hermes.apache.org [209.237.227.199]
Rejected from 209.237.227.199 - see http://spews.org/bounce.html
I understand spews is one of the more aggressive blacklists, but perhaps
one the list admins should look into getting this IP out of spews?
--
Jim Albert
--
Report problems: http
Stas Bekman wrote:
Jim Albert wrote:
Stas Bekman wrote:
Eric Frazier wrote:
Jim, Eric, so can you please put this thread together into one doc
piece that can be added to the docs?
I had just noticed that I received none of the mod_perl mailings in
the past 10 days or so. Looks like the
appropriate environment variables and
open a pipe to my standard CGI. That might work, but it seems messy.
--
Jim Albert
Frank Wiles wrote:
On Tue, 11 Jan 2005 14:02:00 -0500
Jim Albert <[EMAIL PROTECTED]> wrote:
Under mod_perl1 I had a mod_perled program that opened a pipe to a
standard CGI and recorded its output.
I did this in my mod_perl program by setting the following ENV vars:
$ENV{"QUERY_ST
hould eventually expect all modules to move from Apache:: to
Apache2:: or what the criteria might be for doing so. For example, it
looks to me from cpan like Apache::Session still exists in Apache::
Thanks.
--
Jim Albert
Philip M. Gollucci wrote:
Jim Albert wrote:
Can someone point me to a URL that describes the purpose of the
Apache2 namespace?
I don't believe one exists (yet) ... possibly a good idea for the
perl.apache.org site?
The general idea as I've got it is:
1. Apache::*
Mo
Philip M. Gollucci wrote:
Philip M. Gollucci wrote:
Jim Albert wrote:
For example, one piece of my code has
use Apache::Const
but I had to change that to use Apache2::Const on the server running
the lastest mod_perl.
Can you give me the logic to handle that properly in a single code
e base (my code) in terms of whether to include modules from the
Apache:: or Apache2:: namespace. Perhaps the exsitence of and the
particular value of $ENV{MOD_PERL_API_VERSION} might be better suited.
--
Jim Albert
changed from
another version of CGI.pm on a different system where this works fine.
--
Jim Albert
is to
add the following to all my mod_perled scripts that use CGI.pm:
CGI::initialize_globals();
I hope you can help with this.
Jim Albert wrote:
I'm trying to debug a strange situation with the following environment:
Apache 2.0.54
mod_perl 2.0.1
perl 5.8.6
CGI.pm 3.10
Linux 2.6.12-1.1447_
like retrieving input from QUERY_STRING and working
with cookies, please point me to what you use for this.
Thanks.
Jim Albert wrote:
I think I may now have a better understanding of this and that the
problem lies in CGI.pm. I've emailed the following to Lincoln Stein
explaining w
Michael Peters wrote:
Jim Albert wrote:
Lack of response on this tells me:
1. Nobody is using ModPerl::PerlRun any longer to run their scripts
under mod_perl. I doubt it.
From the docs:
This module is meant for "Dirty" CGI Perl scripts
and
The Apache::Registry handl
Perrin Harkins wrote:
On Thu, 2005-10-06 at 11:53 -0400, Jim Albert wrote:
Besides the fact that if I choose
the scripts to run mod_cgi perhaps in a non mod_perl environment,
then
they are all set to go.
This is true with Registry scripts as well.
I thought this was safer than calling
specific keywords, because I
don't believe all the graphics modules are in that list. For example,
I've used Image::Magick for doing some basic image resizing and
conversion, but I don't see Image::Magick in that list.
--
Jim Albert
On 4/23/2013 11:49 AM, Ryan Perry wrote:
I've been plagued by some bug that makes a call to LWP stop working:
"Can't connect to 192.168.0.222 (Bad hostname)"
I haven't been able to figure out why, but a simple httpd restart fixes
it for a day or 2.
Since I can't figure out a real fix, I'm wonde
On 4/23/2013 1:08 PM, Ryan Perry wrote:
I've considered doing it daily via cron, but if there's a way to do when
I hit this error I'd prefer that.
On Tue, Apr 23, 2013 at 12:02 PM, Jim Albert mailto:j...@netrition.com>> wrote:
On 4/23/2013 11:49 AM, Ryan Perry wrot
On 4/23/2013 1:36 PM, Ryan Perry wrote:
On Tue, Apr 23, 2013 at 12:23 PM, Jim Albert mailto:j...@netrition.com>> wrote:
On 4/23/2013 1:08 PM, Ryan Perry wrote:
I've considered doing it daily via cron, but if there's a way to
do when
I hit this
On 4/23/2013 2:33 PM, Ryan Perry wrote:
On Tue, Apr 23, 2013 at 12:47 PM, Jim Albert mailto:j...@netrition.com>> wrote:
On 4/23/2013 1:36 PM, Ryan Perry wrote:
On Tue, Apr 23, 2013 at 12:23 PM, Jim Albert mailto:j...@netrition.com>
<mailto:j...@netrition.c
On 4/23/2013 3:09 PM, Jim Albert wrote:
On 4/23/2013 2:33 PM, Ryan Perry wrote:
On Tue, Apr 23, 2013 at 12:47 PM, Jim Albert mailto:j...@netrition.com>> wrote:
On 4/23/2013 1:36 PM, Ryan Perry wrote:
On Tue, Apr 23, 2013 at 12:23 PM, Jim Albert mailto:j...@netriti
On 4/23/2013 3:27 PM, Ryan Perry wrote:
On Tue, Apr 23, 2013 at 2:09 PM, Jim Albert mailto:j...@netrition.com>> wrote:
On 4/23/2013 2:33 PM, Ryan Perry wrote:
On Tue, Apr 23, 2013 at 12:47 PM, Jim Albert mailto:j...@netrition.com>
<mailto:j...@netrition.c
Not that I want to be the guy that says it sounds like we'll be pulling
the mod_perl plug at any time the right scenario arises, but is it
reasonable to have a discussion here on mod_perl alternatives inline
with the various means of using mod_perl from the low level means of
interfacing with t
27;s what will happen.
Adam
On 3/17/2021 9:50 PM, Jim Albert wrote:
Not that I want to be the guy that says it sounds like we'll be
pulling the mod_perl plug at any time the right scenario arises, but
is it reasonable to have a discussion here on mod_perl alternatives
inline with the va
Given the recent discussion on the need for mod_perl PMC members and the
disclosure that there is no active development on mod_perl this seems
like an appropriate time to start a thread on a discussion of mod_perl
alternatives inline with the various means of using mod_perl from the
low level u
, I think that it is up to the
community if, when, and how that happens. That's what the point of this
thread is. If there aren't people that are committed enough to the
project for whatever reason to step up and keep it from going to the
attic, then that's what will happen.
Adam
When mod_perl does come to an end what would an End of Life look like?
I'm told mod_perl is an Apache Software Foundation project. Do Apache
Software Foundation projects have a structured life cycle or do some
just suddenly disappear with no warning given various situations that
result in the n
On 3/18/2021 10:41 AM, Ruben Safir wrote:
On Thu, Mar 18, 2021 at 10:37:02AM -0400, Jim Albert wrote:
When mod_perl does come to an end what would an End of Life look like?
maybe we can focus on keeping it maintained... really.
A secure well written project like modperl doesn't nee
tic is, and what it would mean to get
more context if you're interested in more detail.
Adam
[1] http://attic.apache.org/
Quoting Jim Albert :
When mod_perl does come to an end what would an End of Life look like?
I'm told mod_perl is an Apache Software Foundation project. Do Apache
So
link below
and reading about what the attic is, and what it would mean to get more context
if you're interested in more detail.
Adam
[1] http://attic.apache.org/
Quoting Jim Albert :
When mod_perl does come to an end what would an End of Life look like?
I'm told mod_perl is
32 matches
Mail list logo
