From: Henning Hraban Ramm <hraban@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Patrick Gundlach <patrick@gundla.ch>
Subject: Re: calling ConTeXt as a background process
Date: Thu, 7 Oct 2010 17:44:31 +0200 [thread overview]
Message-ID: <42FA8D71-B1E3-4762-B5B7-34664685D99E@fiee.net> (raw)
In-Reply-To: <0E9F8810-A7FC-4C0D-905B-93563778833C@gundla.ch>
Am 2010-10-07 um 12:27 schrieb Patrick Gundlach:
>> How's ConTeXt called in ConTeXtgarden Live? Any special means?
>
> http://github.com/pgundlach/contextlive/blob/master/runtexexec.c
>
> I use fork()/exec() combination in C.
Ok, I won't use C...
I guess it's a problem of my specific combination of Ubuntu/SElinux,
Django/fcgi and LuaTeX... :-(
I found others running latex from Django in exactly the same matter as
ConTeXt fails for me.
But I can call other programs that way, so part of the problem is in
LuaTeX.
Greetlings, Hraban
___________________________________________________________________________________
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:[~2010-10-07 15:44 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 7:06 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
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 [this message]
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=42FA8D71-B1E3-4762-B5B7-34664685D99E@fiee.net \
--to=hraban@fiee.net \
--cc=ntg-context@ntg.nl \
--cc=patrick@gundla.ch \
/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).