ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: Taco Hoekwater <taco@elvenkind.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: calling ConTeXt as a background process (SOLVED)
Date: Tue, 26 Oct 2010 23:32:12 +0200	[thread overview]
Message-ID: <4CC748DC.6040201@wxs.nl> (raw)
In-Reply-To: <4CC74086.4090906@elvenkind.com>

On 26-10-2010 10:56, Taco Hoekwater wrote:
>
>
> On 10/26/10 22:09, Hans Hagen wrote:
>> On 26-10-2010 9:28, Taco Hoekwater wrote:
>>>
>>> Hi Henning,
>>>
>>> On 10/08/10 21:44, Henning Hraban Ramm wrote:
>>>> Ok, the failures were the same with fcgi and gunicorn app servers.
>>>>
>>>> But it _works_ with django's dev server (which you must not use in
>>>> production due to memory/security holes etc.).
>>>
>>> We just had a somewhat similar problem (texlua hung at 100% cpu
>>> when run via apache) and it turns out, after lots of debugging,
>>> that mtxrun cannot do anything without $HOME. Perhaps yours was
>>> a different symptom of the same problem ?
>>>
>>> try this if you want to test CPU heat generation:
>>>
>>>     $ env HOME= context knuth
>>
>> so what should HOME default to then? "."?
>
> Not a default is what is needed, what is needed is that it should work
> without a HOME at all (server processes typically dont have one).

sure, but I guess that some path specs have ~ and that we get a loop in 
the resolver due to this and for these patsh with ~ we need a proper 
default then

> Let's sort this out offlist.

okay

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2010-10-26 21:32 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07  7:06 calling ConTeXt as a background process Henning Hraban Ramm
2010-10-07  7:34 ` Henning Hraban Ramm
2010-10-07  8:42   ` Taco Hoekwater
2010-10-07  9:00     ` Henning Hraban Ramm
2010-10-07  9:06       ` Taco Hoekwater
2010-10-07 10:19         ` Henning Hraban Ramm
     [not found]           ` <90F33E64-7BB9-4DEB-9E89-A4FC99169401@awi.de>
2010-10-07 15:55             ` Henning Hraban Ramm
2010-10-07 16:32               ` Florian Wobbe
2010-10-08  7:36                 ` Henning Hraban Ramm
2010-10-08  7:59                   ` Florian Wobbe
2010-10-08  8:43                     ` Henning Hraban Ramm
2010-10-08  9:25                       ` Florian Wobbe
2010-10-08 10:00                         ` Henning Hraban Ramm
2010-10-08 11:46                           ` Florian Wobbe
2010-10-08 13:47                             ` Henning Hraban Ramm
2010-10-08 13:54                               ` luigi scarso
2010-10-08 13:54                               ` Taco Hoekwater
2010-10-08 14:22                                 ` Patrick Gundlach
2010-10-08 14:30                                 ` Henning Hraban Ramm
2010-10-08 14:57                                   ` Taco Hoekwater
2010-10-08 15:10                                     ` Hans Hagen
2010-10-08 15:08                                   ` Florian Wobbe
2010-10-08 19:44                                     ` calling ConTeXt as a background process (SOLVED) Henning Hraban Ramm
2010-10-10  8:47                                       ` Patrick Gundlach
2010-10-10  9:01                                         ` Henning Hraban Ramm
2010-10-26 19:28                                       ` Taco Hoekwater
2010-10-26 20:09                                         ` Hans Hagen
2010-10-26 20:56                                           ` Taco Hoekwater
2010-10-26 21:32                                             ` Hans Hagen [this message]
2010-10-26 20:13                                         ` Henning Hraban Ramm
2010-10-08 15:05                                 ` calling ConTeXt as a background process Henning Hraban Ramm
2010-10-07 18:16               ` taco
2010-10-08  8:00                 ` Henning Hraban Ramm
2010-10-08  8:12                   ` Patrick Gundlach
2010-10-08  9:21                     ` Henning Hraban Ramm
2010-10-08  9:27                       ` luigi scarso
2010-10-08  8:37                   ` luigi scarso
2010-10-08  8:47                     ` Henning Hraban Ramm
2010-10-08  8:54                       ` luigi scarso
2010-10-08 10:19                   ` Hans Hagen
2010-10-07 10:16       ` Robin.Kirkham
2010-10-07 11:02         ` Henning Hraban Ramm
2010-10-07 10:27       ` Patrick Gundlach
2010-10-07 15:44         ` Henning Hraban Ramm
2010-10-07 15:48           ` luigi scarso
2010-10-07 16:15             ` Henning Hraban Ramm

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=4CC748DC.6040201@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=taco@elvenkind.com \
    /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).