Am 2010-10-10 um 10:47 schrieb Patrick Gundlach:
Thank you all for your patience, ideas and help!
Sorry, that I didn't quite understand the problem/solution, could
you describe in a few sentences what problem was and how you solved
it?
I actually couldn't find out what the real problem was. ;-)
I tried to start ConTeXt from a Django web application server.
(Running ConTeXt from an active shell was no problem.)
My Django FCGI processes were running under daemontools (http://cr.yp.to/daemontools.html
) supervision, i.e. started by its supervise daemon.
In this setup, texlua hung at least at uname (and maybe other) calls.
I found no error messages on that, I guess the environment was
restricted in some way.
Since I thought it might have to do with the FCGI server, I replaced
that by Green Unicorn (http://gunicorn.org/), but that made no
difference WRT ConTeXt.
When I changed process supervision from daemontools to supervisor (http://supervisord.org/
), I got no further problems.
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the
Wiki!
maillist : [email protected] / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
