Stas Bekman 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?
so any chance someone can put together the solutions from Eric and Jim,
and the other suggestions I gave in the reply to the Jim's ori
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?
so any chance someone can put together the solutions from Eric and Jim,
and the other suggestions I gave in the reply to the Jim's original
question? And
On Wednesday, 2004-06-30 at 13:42:16 -0700, Eric Frazier wrote:
> Who ever is admining your mail server might want to look into using a
> *responsible* list. Spews routinely causes horror for many innocents,
> sometimes blocking whole datacenters over one account.
For this partivular case, plea
Hi,
Who ever is admining your mail server might want to look into using a
*responsible* list. Spews routinely causes horror for many innocents,
sometimes blocking whole datacenters over one account.
Almost any other list is an improvement, I have noticed many lists follow
along behind http://ww
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 mod_per
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 mod_perl list mail server
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 mod_perl list mail server is on a
spam blac
Eric Frazier wrote:
Jim, Eric, so can you please put this thread together into one doc piece that
can be added to the docs?
--
__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guid
Hi,
Very glad I could be of some help, even though most of this was copy and paste and
googling. I was in fact testing this on a FreeBSD server with 5.8.0, the production
server is 5.8.4.
Eric
At 03:39 PM 6/15/2004, Jim Albert wrote:
>Great! It's always nice to have multiple solutions to a p
Jim,
Thank you! This was a big help to me in that I ran into this problem from two
directions recently, with a perl daemon and with Apache::SIG.. I did find some info
about fixing this for real rather than using unsafe signals. They mostly seemed to
point to using the POSIX sigaction methods ra
Great! It's always nice to have multiple solutions to a problem. I
believe Stas Bekman also pointed to the POSIX sigaction solution when he
first pointed me in the right direction in solving this problem, but
setting $ENV{PERL_SIGNALS} = "unsafe"; got me going with perl 5.8 very
quickly.
I mi
Last week I had a problem where I could not get my
Apache2/mod_perl2/perl5.8.3 web server to catch a SIGPIPE signal in a
timely manner. I was asked to post a description of this problem and
solution to this list so that it might be included in future mod_perl
documentation.
Feel free to adjus
12 matches
Mail list logo
