Skip to content

Conversation

@dnorman
Copy link

@dnorman dnorman commented Jun 4, 2011

Perhaps I'm being an idiot, but why does FCGI seem to hate STDERR?

This patch allows your to un-roundfile STDERR, because I can see no other way to easily debug code.

Thoughts?
Daniel-

@stevan
Copy link
Owner

stevan commented Jul 6, 2011

Daniel,

Sorry it took so long to get back to you on this. Typically FCGI sends the STDERR back to the web-server and it ends up in the error-log. Are you not seeing this behavior? Or is this not working correctly? Basically, could you elaborate more on your use case?

  • Stevan

@dnorman
Copy link
Author

dnorman commented Jul 6, 2011

yeah, for some reason though, STDERR didn't seem to come through into the web server's error log, thus the hack.
I was using lighttpd.

@stevan
Copy link
Owner

stevan commented Jul 6, 2011

You need to actually put "fastcgi.debug = 1" into your lighttpd config to make it capture STDERR as expected. Perhaps that will solve your issue?

@dnorman
Copy link
Author

dnorman commented Jul 6, 2011

aha, you're probably right about that one. None-the-less, it would be nice to have a flag to show STDERR on the console, as does the catalyst fastcgi script with the -e flag

@stevan
Copy link
Owner

stevan commented Jul 6, 2011

Yeah I think we can integrate it, would you including some documentation on it? Perhaps even a test?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants