That was it. I redefined Sig{__WARN__} to drop all STDERR output and my
script output everything it was supposed to and exited cleanly. Now
there is another bug that undoubtedly came from my trying to track down
the original issue...
Thanks. That saved me a ton of time.
Tom
Terra Info wrote:
[When starting a new thread, please remember to create a new mail,
rather than doing a reply to one of the threads. If you don't do that,
your mail software attaches reference ids to the original thread and
your post gets folded into the thread you've replied to. people may
delete the whole
The threads issue is my bag. I know better but was busy and distracted,
hence I just did a reply to all and trimmed out the excess. Anyhow, I
think you may have misunderstood my question. Although I have a specific
issue at hand, my question was more generic. My questions are more
related to
Terra Info wrote:
The threads issue is my bag. I know better but was busy and distracted,
hence I just did a reply to all and trimmed out the excess.
No prob. the comment was addressed to all subscribers.
Anyhow, I
think you may have misunderstood my question. Although I have a specific
Stas Bekman wrote:
I still don't understand you. When do you see the problem? When you
run the script under mod_cgi or mod_perl? I don't understand why do
you keep referring to mod_cgi.
And we are talking about Apache/mod_perl 2.0 here, right?
No. I am talking about mod_cgi when I say
OK, now it's clear, thanks for the explanation. FWIW, there were
discussions of possible pipes read/write deadlocks in the current
mod_cgi implementation in Apache 2.0, so you may experience just that.
Check the httpd-dev list archives.
[...]
* Given that, I noticed PerlRun was no longer
Ugh! I checked the users list archives but I never checked the dev
archives. I liked p5p back in the day because it was all one in the
same. Chaos, but oddly efficient. Thanks for the pointer.
As for the docs, I freely admit I missed it. I was not looking for
PerlRun stuff when I went through
