Doh! I avoid doing system calls to external apps like the plague so I
forget things like that.
Thanks for catching it,
Tom
Stas Bekman wrote:
Terra Info wrote:
[...]
application. If you would like to take output from that application
then
you should write to STDOUT all text you want the perl
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
Two things: 1) this is not the list for this question.
2) a probable answer anyhow-
The issue is not file permissions (per se) or anything like that. It is
the way WinNT and up is built. What you were doing in Win 98 worked
because apps all ran in the same user space. Despite logging into a 98
I am debugging a particularly nasty issue right now on a perl script
that when written 2+ yrs ago worked fine. NB: It does not run under
mod_perl and it has not been modified since then. I run it from the cmd
line (with the identical query string and all referenced %ENV vars set
identical as
to the original thread and
your post gets folded into the thread you've replied to. people may
delete the whole thread without seeing your post if they weren't
interested in this thread. it also has an ill effect on mail archives.]
Terra Info wrote:
I am debugging a particularly nasty issue right
;-}.
Tom
Stas Bekman wrote:
Terra Info wrote:
Two things: 1) this is not the list for this question.
2) a probable answer anyhow-
If that's a real pitfall and it's doomed to be a recurrent question,
can we please document this under win32/? Also, Randy, it seems that
there is whole lot
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
.
Tom
Stas Bekman wrote:
Terra
Info wrote:
I will write up a more publically palatable
version of the below and post it for someone more intimately
associated with the docs and development to merge into the tree.
Great, thank you!
Keep in mind that this is an issue not just
for MP
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
Sounds good. Thanks for the help. I will patch my copy. Will all MP1
functionality be migrating over to MP2? In particular the PerlHandler
Apache::Status functionality.
Thanks,
Tom
Stas Bekman wrote:
Terra Info wrote:
PS: I forgot to let you know if it works on MP1. I do not have
{$status}[0]);
$retstr .= sprintf(Status: %s %s\n, 404, 'Object Not Found!');
$retstr .= \n;
$retstr .= 'htmlheadtitleError 404: Object Not
Found!/title/headbody bgcolor=#FFh2Error 404: Object Not
Found!/h2pBlah, blah, blah.../p/body/html';
print($retstr);
exit;
Stas Bekman wrote:
Terra
PS: I forgot to let you know if it works on MP1. I do not have that
installed on any machines so if someone out there on the list could
check that out and post back I would appreciate it. Everything you need
is below.
Tom
Terra Info wrote:
Thanks for the help. Below is all the info you
I have a script that provides custom error messages that I set up using
the ErrorDocument directive (ie; ErrorDocument 400
/cgi-global/error.pl?error=400useXML=1). When run under typical mod_cgi
all works as planned and it outputs the proper stuff. When run under
mod_perl it outputs the same
13 matches
Mail list logo
