mod_perl, php, mason segmentation fault

2005-06-27 Thread jiesheng zhang
Hi, My system is as this Apache/1.3.33 (Darwin) PHP/4.3.11 mod_perl/1.26. The system worked fine until I installed mason script on it recently. When I tried to browse a page backed up by mason script, I get an empty page and the apache error log has this message "[Mon Jun 27 06:24:35 2005] [noti

Re: compile mod_perl with Apache::DBI support

2005-05-02 Thread jiesheng zhang
Perrin Harkins wrote: On Tue, 2005-05-03 at 00:21 +0800, jiesheng zhang wrote: I saw debug information in the apache log file after I added the use Apache::DBI to the startup.pl. However, this is not mentioned in the Apache::DBI documentation. The documentation only mentioned that I should add

Re: compile mod_perl with Apache::DBI support

2005-05-02 Thread jiesheng zhang
Perrin Harkins wrote: On Mon, 2005-05-02 at 20:10 +0800, jiesheng zhang wrote: I indeed set the $Apache::DBI::DEBUG=2 in the /etc/apache2/mod_perl-startup.pl. However I did not see any debug output in the apache error log file Did you "use Apache::DBI" in your startup.pl or

Re: compile mod_perl with Apache::DBI support

2005-05-02 Thread jiesheng zhang
I am using the SuSE 9.1 which has apache 2.0 and mod_perl 1.99_12. I did not see any Apache::DBI debug information in the apache error log. jiesheng, please read the module's manpage: http://search.cpan.org/dist/Apache-DBI/DBI.pm To enable debugging the variable $Apache::DBI::DEBUG must be set

compile mod_perl with Apache::DBI support

2005-05-01 Thread jiesheng zhang
I am using the SuSE 9.1 which has apache 2.0 and mod_perl 1.99_12. I did not see any Apache::DBI debug information in the apache error log. I guessED the the mod_perl is not complied with the EVERYTHING=1 option. I then tried to compile the mod_perl to support Apache::DBI The perl configuration c

for a background process and return

2005-04-29 Thread jiesheng zhang
Hi I am try to run something like this in my cgi. - system ("sleep 3000 &"); --- Since, it is time-consuming task, I let it run in background and immediately return to user. I tested this script. It was no problem for a standalon