From: Raymond LeClair <raymond.leclair@synterein.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Would Multiple Processes Cause: luatex: execution interrupted
Date: Tue, 5 Jul 2011 11:15:24 -0400 [thread overview]
Message-ID: <C52472CD-100B-46F8-B927-2EDA2CE2E8D3@synterein.com> (raw)
In-Reply-To: <4E12ABF1.20700@elvenkind.com>
Taco,
Thanks for your reply!
You are correct, the issue appears to be memory. The system is hosted on a linode, the smallest of which is 512 MB RAM. I increased this to 1024 MB RAM and this appears to fix the problem.
Very much appreciate your help.
Ray.
On Jul 5, 2011, at 2:15 AM, Taco Hoekwater wrote:
> On 07/05/2011 08:11 AM, luigi scarso wrote:
>> On Tue, Jul 5, 2011 at 4:23 AM, Raymond LeClair
>> <raymond.leclair@synterein.com> wrote:
>>> Thanks for your reply!
>>>
>>> On Jul 4, 2011, at 5:35 PM, Taco Hoekwater wrote:
>>>
>>>> Quite possibly (but that is very hard to verify and would be even harder to debug). Best practise is to give each process its own temporary directory, just in case.
>>>
>>> This is, in fact, guaranteed by design: each file resides in a directly which is named using a uuid.
>>>
>>> Is it possible that context or luatex are creating files in a common directory, say the cache directory, and access by one process locks the file for access by another?
>> It's possible: say for example that each task rebuild the format at
>> every run just to be sure. The format is shared by all instances for
>> the same minimals or TeXLive, so conflicts may arise.
>> The same for example for the font cache.
>
> Possible but, I think, quite unlikely. Another possibility is that you simply run out of memory?
>
> Best wishes,
> Taco
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2011-07-05 15:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 21:24 Raymond LeClair
2011-07-04 21:35 ` Taco Hoekwater
2011-07-05 2:23 ` Raymond LeClair
2011-07-05 6:11 ` luigi scarso
2011-07-05 6:15 ` Taco Hoekwater
2011-07-05 15:15 ` Raymond LeClair [this message]
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=C52472CD-100B-46F8-B927-2EDA2CE2E8D3@synterein.com \
--to=raymond.leclair@synterein.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).