ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Brendan Jurd <brendan.jurd@achievecorp.com.au>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [SOLVED] mod_php vs context: tight loop
Date: Fri, 02 Dec 2011 12:59:32 +1100	[thread overview]
Message-ID: <4ED83104.2030404@achievecorp.com.au> (raw)
In-Reply-To: <4ED1CE7C.3080001@achievecorp.com.au>

On 27/11/11 16:45, Brendan Jurd wrote:
> 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.
>>>
>> in such cases I always run with --batch to make sure that the job
>> itself cannot block
>
> Thanks for the response. I tried running with --batch and it made no
> difference to the outcome. The mtxrun process still got jammed up in
> exactly the same manner.
>
> Regressing to the ubuntu 'lucid' packages resolved the problem for me,
> so whatever is wrong has gone wrong somewhere in the combination of
> packages in ubuntu 'natty'.
>

I did eventually get to the bottom of this.  Turns out that mtxrun was 
failing to find a writable cache path (from mtxrun line 9269).

To find a cache path, mtxrun searches through the environment variables 
TEXMFCACHE, TMPDIR, TEMPDIR, TMP, TEMP, HOME, HOMEPATH.

The apache worker process had no such environment variables, so mtxrun 
failed.  Once I added the following line to my PHP script, everything 
started working just fine:

putenv('TEMPDIR=/tmp');

-- 
Regards,
Brendan Jurd

Software Engineer
Achieve, Corp

brendan.jurd@achievecorp.com.au
___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2011-12-02  1:59 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
2011-12-02  1:59     ` Brendan Jurd [this message]
2011-12-02 10:31       ` [SOLVED] " 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=4ED83104.2030404@achievecorp.com.au \
    --to=brendan.jurd@achievecorp.com.au \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).