On Thu, Jul 31, 2008 at 6:37 PM, Don Stewart [EMAIL PROTECTED] wrote:
agentzh:
On Thu, Jul 31, 2008 at 1:56 AM, Don Stewart [EMAIL PROTECTED] wrote:
We've had no problems with this and apache at least. Is lighttpd
doing something funny with error logging?
It seems that Apache is doing
On Thu, Jul 31, 2008 at 1:56 AM, Don Stewart [EMAIL PROTECTED] wrote:
We've had no problems with this and apache at least. Is lighttpd
doing something funny with error logging?
It seems that Apache is doing something funny :) According to my
teammate chaoslawful, apache redirects stderr to its
agentzh:
On Thu, Jul 31, 2008 at 1:56 AM, Don Stewart [EMAIL PROTECTED] wrote:
We've had no problems with this and apache at least. Is lighttpd
doing something funny with error logging?
It seems that Apache is doing something funny :) According to my
teammate chaoslawful, apache
agentzh:
Hi,
I'm trying Network.FastCGI + lighttpd 1.4.9 to develop a RESTful
service platform. I've found that stderr (especially those from
Debug.Trace) get lost in the error.log file. But plain CGI mode with
Network.CGI works perfectly (all stderr outputs appear in error.log).
Besides,
