Hello, im very new to the perl, modperl and apache combination.
I was wondering if it is somehow possible to read the apache error.log input
just after each execution of a procedure?
I am invoking another program from within my perl module using a
'System(...)' call. Although the call is
Hello, im very new to the perl, modperl and apache combination.
So am I, but I think I have a usable solution for you.
I am invoking another program from within my perl module using a
'System(...)' call. Although the call is successfull, there are times when
the invoked program may
thanks Rodger,
I had Initially tried using 'eval' however it seemed to me that no
exceptions were thrown by the function call within the eval {system...} but
within the called program itself, I may be wrong. In either case that method
brought me no success unfortunately.
From: Rodger Castle
I had Initially tried using 'eval' however it seemed to me that no
exceptions were thrown by the function call within the eval {system...} but
within the called program itself, I may be wrong. In either case that method
brought me no success unfortunately.
Admittedly, I should have read
Admittedly, I should have read your original post more closely. The program
your calling with system fails, not the system call itself, so eval would not
catch this. Have you considered using the backtick operator and inspect the
output for errors? This might not be feasible if the
Femi Oshagbemi wrote:
Hello, im very new to the perl, modperl and apache combination.
I was wondering if it is somehow possible to read the apache error.log
input just after each execution of a procedure?
I am invoking another program from within my perl module using a
'System(...)' call.
Nick *** wrote:
We can do that. But it should be done in one place and not repeated in all
files. So could you apply this patch:
[...]
and then s/static/MP_STATIC/ in all the places you have a problem with and
resubmit a new patch?
Thanks.
There it is :)
Thanks Nick, committed.
--
Hi all,
The following Apache CPAN modules are looking for new owners:
1) Apache-DebugFilter (mp2)
http://search.cpan.org/dist/Apache-DebugFilter/
2) Apache-Filter-HTTPHeadersFixup (mp2)
http://search.cpan.org/dist/Apache-Filter-HTTPHeadersFixup/
3) Apache-GTopLimit (mp1, still needs to be
Hi,
Is it possible to upgrade mod_perl from 1.9.9.03 (if I remember well the
number) to the latest version?
Or do I need to remove the old version and install the newest one?
I have a problem with a program (presa.industrialit.ro) because sometimes it
works, I can view a page, click a link view
Hi
Has Apache::Request been Ported to mod perl 2 yet? What is
the
recommended way to read Request Parameters under mod perl
2?
thx
- Praveen
__
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
Octavian Rasnita wrote:
Hi,
Is it possible to upgrade mod_perl from 1.9.9.03 (if I remember well the
number) to the latest version?
Or do I need to remove the old version and install the newest one?
No problem at the moment to do 1.99_03 to 1.999_22, it should overwrite
the old install w/o
You can get Apache::Request for mod_perl 2 from the apache website.
Please note that if you use the -upload feature that you might want to
pull down a version out of svn as it is buggy in the released tarball.
On Sun, 27 Mar 2005, Praveen Ray wrote:
Hi
Has Apache::Request been Ported to mod perl
* D. Hageman shaped the electrons to say...
You can get Apache::Request for mod_perl 2 from the apache website.
Please note that if you use the -upload feature that you might want to
pull down a version out of svn as it is buggy in the released tarball.
Speaking of - when will there be another
Author: stas
Date: Sun Mar 27 07:21:07 2005
New Revision: 159153
URL: http://svn.apache.org/viewcvs?view=revrev=159153
Log:
cygwin fixes:
- doesn't like XS wrapper starting with 'static'
- need to compile everything with -DCYGWIN
Contributed by: Nick *** [EMAIL PROTECTED]
Modified:
14 matches
Mail list logo
