Re: Warnings awol in Win32 mod

Although I'm unable to tell why is not working, I think I can give you at least a workaround: why don't you use Log4perl instead of relying in warn going to Apache log´s? Even if you start using just the "fast and dirty" mode, I think is worth of it.

By experience, using WindowsXP to do anything that you would like to do in a server is a problem. Things just don't work like they are suppose to, like FastCGI and Cygwin, for example. You may want to check the possibility to use a differente version of Windows or use IIS with the ActivePerl binding (PerlEx) to get the speed improvement.

Alceu Rodrigues de Freitas Junior
---------------------------------
"You have enemies? Good. That means you've stood up for something, sometime in your life." - Sir Winston Churchill

Comment on Re: Warnings awol in Win32 mod_perl. Download Code

Replies are listed 'Best First'.
Re^2: Warnings awol in Win32 mod_perl. by fenLisesi (Priest) on Apr 26, 2007 at 13:03 UTC
I guess we will consider Log::Log4perl and similar options if all else fails, unless, the consensus here is that I should be using them in any case. I would have to study whether such workarounds would recover warnings from perl as well. XP is my friend's dev environment. The internal staging deployment is on 2003 Server and we see the same behavior there, too.	[reply]