ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Re: ConTeXt "live"
Date: Sat, 03 Dec 2005 12:56:04 +0100	[thread overview]
Message-ID: <439187D4.1050801@elvenkind.com> (raw)
In-Reply-To: <m2acfjdw5k.fsf@levana.de>

Patrick Gundlach wrote:
> Hi,
> 
> 
>>In my account, ConTeXt works no prob, I got a perfect PDF.
>>My problem occurs when I run ConTeXt via web, under Apache's user of course.
>>How to trace ConTeXt run under web server ?

Reversing the order will hopefully give a clue on how to proceed:
make ConTeXt create mpgraph.mp first, then the other one. If that
gets you past the error (and into a similar error: test-mpgraph.mp),
then it is probably a  number of open files limit problem. Here is
the relevant macro, with the order already adjusted :

\def\initializeMPgraphics
   {\bgroup
    \ifx\bufferprefix\empty\else
      \let\bufferprefix\empty
      \initializeMPgraphicfile
    \fi
    \egroup
    \initializeMPgraphicfile }

> I'd guess it is pretty much impossible to trace under a webserver. Can
> you install the same environment on a local computer? Then you could
> strace any process.

You can try to add --passon='-kpathsea-debug=4' in the texexec
call. All the kpathsea debug output should end up in your apache
error_log (the number 4 is for fopen/fclose traces).

> Perhaps this is a problem with php? Did you try running this via cgi?

If you are lucky, there may be some hint in your global or local
apache error file.


Good luck,

Taco

  reply	other threads:[~2005-12-03 11:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-01 22:19 VnPenguin
2005-12-02 14:05 ` Hans Hagen
2005-12-02 14:25   ` VnPenguin
2005-12-02 15:17     ` Hans Hagen
2005-12-02 14:21 ` Patrick Gundlach
2005-12-02 14:30   ` VnPenguin
2005-12-02 15:17     ` Patrick Gundlach
2005-12-02 18:32       ` VnPenguin
2005-12-02 21:30         ` Patrick Gundlach
2005-12-03 11:56           ` Taco Hoekwater [this message]
2005-12-03 23:10           ` Christopher Creutzig
2005-12-04  0:13             ` Patrick Gundlach
2005-12-02 15:32     ` Hans Hagen

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=439187D4.1050801@elvenkind.com \
    --to=taco@elvenkind.com \
    --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).