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 Hoek
On 07/05/2011 08:11 AM, luigi scarso wrote:
On Tue, Jul 5, 2011 at 4:23 AM, Raymond LeClair
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 pro
On Tue, Jul 5, 2011 at 4:23 AM, Raymond LeClair
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,
>>
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
On 4 jul. 2011, at 23:24, Raymond LeClair wrote:
> I run context in a task queue with four worker processes. It is possible that
> context is invoked simultaneously to process distinct input files by tasks
> running in separate worker processes. I see periodic fatal errors, as follows:
>
>
I run context in a task queue with four worker processes. It is possible that
context is invoked simultaneously to process distinct input files by tasks
running in separate worker processes. I see periodic fatal errors, as follows:
mtx-context | fatal error: no return code, message: luatex:
