From: Henning Hraban Ramm <hraban@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: mod_php vs context: tight loop
Date: Sun, 27 Nov 2011 10:53:02 +0100 [thread overview]
Message-ID: <0818B6F7-CA87-48EE-B73E-288384D76D47@fiee.net> (raw)
In-Reply-To: <4ED1CE7C.3080001@achievecorp.com.au>
Am 2011-11-27 um 06:45 schrieb Brendan Jurd:
> On 25/11/11 19:17, Hans Hagen wrote:
>> On 25-11-2011 06:12, Brendan Jurd wrote:
>>> I have a PHP application which generates documentation on the fly
>>> with
>>> context. This has been working really well, but I am now testing
>>> deployment on a new server with a more recent version of context,
>>> and it
>>> seems to be somehow getting itself into a tight loop.
Hi Brendan,
I once had similar problems running ConTeXt (LuaTeX) behind my Django
server (gunicorn or FCGI behind Nginx).
In my case it was some strange permissions problem of the calling
process.
I could only avoid it by changing my process manager from daemontools
to supervisord.
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 : ntg-context@ntg.nl / 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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-11-27 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 5:12 Brendan Jurd
2011-11-25 8:17 ` Hans Hagen
2011-11-27 5:45 ` Brendan Jurd
2011-11-27 9:53 ` Henning Hraban Ramm [this message]
2011-12-02 1:59 ` [SOLVED] " Brendan Jurd
2011-12-02 10:31 ` Hans Hagen
2012-01-03 20:46 ` Brendan Jurd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0818B6F7-CA87-48EE-B73E-288384D76D47@fiee.net \
--to=hraban@fiee.net \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).