Ron Savage wrote:
FolksI wonder why do you get the timestamp in first place, Apache::Reload does:
I don't know if this an Apache problem, or a mod_perl problem.
Apache::Reload outputs a UTC date rather than a local date, when it encounters an error. Here's an excerpt from my log.
Notice how the dates go Sun, Mon, ..., Sun.
[Sun Feb 16 18:31:25 2003] [error] [client 127.0.0.1] Execution of C:/Apache2/cgi-bin/test/test-path-info.cgi aborted due to compilation errors., referer: http://127.0.0.1/cgi-bin/test/test-path-info.cgi
[Mon Feb 17 10:44:04 2003] [error] [client 127.0.0.1] Premature end of script headers: menu-process-module.cgi, referer: http://127.0.0.1/cgi-bin/menu-process-module.cgi
[Mon Feb 17 10:44:04 2003] [error] [client 127.0.0.1] Can't locate Module/MakeDist.pm in @INC (@INC contains: C:/Perl/lib C:/Perl/site/lib .) at C:/Apache2/cgi-bin/menu-process-module.cgi line 15., referer: http://127.0.0.1/cgi-bin/menu-process-module.cgi
[Mon Feb 17 10:44:04 2003] [error] [client 127.0.0.1] BEGIN failed--compilation aborted at C:/Apache2/cgi-bin/menu-process-module.cgi line 15., referer: http://127.0.0.1/cgi-bin/menu-process-module.cgi
[Sun Feb 16 23:49:41 2003] -e: Apache::Reload: Can't locate C:/Perl/site/lib//CGI/Explorer.pm
warn("Apache::Reload: Can't locate $file\n"), next
unless defined $mtime and $mtime;
which is a pure perl call. Or does perl on windows adds a timestamp when loggin warnings? In any case, I doubt this has anything to do with mod_perl. The [client 127.0.0.1] errors come from Apache, Apache::Reload warnings are coming from perl. check what do you get when you run:
perl -le 'warn("foo\n")'
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
