On 29 Feb., 21:38, tamas kemenczy <[EMAIL PROTECTED]> wrote: > Recently at work I've encountered a need to be able to redirect the > stdout/stderr of a daemonized fastcgi Django process to a log file > (something other than /dev/null).
This is very interesting for me, too. Can you post you existing code in a django ticket? btw. i have problems to setup a fastCGI app in a non root environment. If something is not right, it only helps to look into the Apache error log. But i haven't access to the log file :( Sometimes it helps to activate the flup "low level" debug traceback, but this is deactivated hardcoded with http://code.djangoproject.com/changeset/4170 I have created a patch for this: http://code.djangoproject.com/ticket/6610 Redirect stdout/stderr into a file helps, too. I created a fastCGI dispatcher on the top of the django runfastcgi() function. In this additional layer i implemented a file logging (using the logging module) and a way for catching all possible errors and displayed these with a small own WSGI app. These two files contains the code: http://pylucid.net:8080/pylucid/browser/trunk/pylucid/index.fcgi http://pylucid.net:8080/pylucid/browser/trunk/pylucid/PyLucid/system/fastcgi_server.py Unfortunately, not all errors intercepted :( It would help, if there exist something like a "always reload" mode in tb_catch_app(), but i don't know to implement this. -- Mfg. Jens Diemer ---- A django powered CMS: http://www.pylucid.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
