From: toto tartemolle <lists@...>
Date: 2012-09-10T01:15:06+09:00
Subject: Re: Long calculation & time limit

>If you want to know exactly what part of your program is taking a long
>time, then use something like this to log the intervals

I'm already using a timer. I mentionned earlier that the parts of the
program are supposed to take time. Time taken is not the core problem,
the limitation is.

>ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 20
file size               (blocks, -f) unlimited
pending signals                 (-i) 16382
max locked memory       (kbytes, -l) unlimited
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 99
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) unlimited
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

>Message at full

litterally: "Killed, returned error 137"

-- 
Posted via http://www.ruby-forum.com/.