(cc'ing supervisor list in case anyone else runs into this) Just FYI, I took a look at the issue that we saw on Friday where stdout output from Zope wasn't immediately showing up in the log (particularly the "server ready" lines when Zope first starts up). It turns out that this is has to do with process stdout buffering. If I run paster with a Python shebang with a "-u" after it (unbuffered mode), all is well, or if I put a stdout.flush() after the "server ready" lines, all is well too.
I figured I'd just add "environment = PYTHONUNBUFFERED=t" to the [zope] program section in supervisord.conf, but that doesn't appear to work (although it *is* in the environment when the child is exec'ed). The heavy hammer of starting supervisord via "PYTHONUBUFFERED=t bin/supervisord" *does* work however (the children inherit the environment). Still looking for the right answer. _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
