This problem still exists with django-1.0. I've been researching a bit: http://code.djangoproject.com/changeset/7297 does some changes. It works if I comment out the os.dup2 lines, but that may not be very robust. I'm using threaded model, not fork.
On 12 ago, 18:51, Brian Victor <[EMAIL PROTECTED]> wrote: > To answer your question from your first response, no, I don't have a > solution for this yet. I'm not even sure where to go from here. (For > those listeners just joining us, the topic of conversation is a lack > of error messages and tracebacks in either the fastcgi or lighttpd log > files.) > > That said, > > On Aug 12, 9:22 am, spacetaxi <[EMAIL PROTECTED]> wrote: > > > > - No notification email is sent to the admins listed in > > > settings.ADMINS > > This problem is solved. It had nothing to do with django but with our > > mail server silently discarding some mails. So, sorry for suspecting > > django for causing this problem! > > I didn't even realize this was a feature. That may alleviate my need > somewhat, but it would still be nice to get logging working. Thanks > for pointing it out! > > -- > Brian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
