Hi,
Gerald Richter schrieb:
Hi,
we just startet a new project using Embperl2 / mod-perl2 / Apache2-prefork and have problems with "warn" going to global apache error_log instead of the vhosts error_log (where embperl 1.3.* warnings ended).
Also syntax errors in epl-files are splittet - one line in global error_log, the second in the vhost's log...
That sounds strange. Could you give an example what is going to the global and what to the vhost log?
epl-file:
[- warn "I end up in global error_log" -]
[- waarn("and I in vhosts...."); -]=> /var/log/apache2/error.log <==
I end up in global error_log at /web/data/www.vhost.com/htdocs/error.html line 2.
==> /web/data/www.vhost.com/logs/error.log <==
[Thu Dec 30 15:04:04 2004] [error] [19792]ERR: 24: Error in Perl code: Undefined subroutine &Embperl::__2::waarn called at /web/data/www.vhost.com/htdocs/error.html line 3.
The splittet errors disappeared after upgrading to "the bleeding edge" tonight... sorry, could not reproduce this bug.
I tracked down the problem a bit further:
we use Embperl::Object. If I disable it and only use Embperl, the first warning will be in the right file...
base.epl:
[- Execute("*") -]sites-available/vhost.com (apache2.conf): [...] <FilesMatch ".*\.html?$"> EMBPERL_APPNAME vhostappname EMBPERL_ESCMODE 0 EMBPERL_DEBUG 2301 EMBPERL_OPTIONS 43550 EMBPERL_OBJECT_BASE base.epl EMBPERL_OBJECT_ADDPATH /web/data/our_lib_dir
SetHandler perl-script PerlHandler Embperl::Object Options +ExecCGI </FilesMatch> [...]
Bye,
Dirk Melchers.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
