Michael Norrish wrote:
On 13/05/10 11:01, Michael Norrish wrote:
The presence of "Killed" makes me think that the script is being killed
by an external signal, perhaps a SIGSEGV caused by hitting a limit on
stack-size. But is this plausible? Would Poly/ML catch that signal and
then exit with 89?
Experiments reveal that Poly/ML seems to be exiting with 0x80 +
<signalnumber> when it's sent a signal. The documentation for getrlimit
says that 89 (SIGKILL) might happen if the hard time limit on the
process was being reached. So, my current guess is that my cronjob is
being time-limited.
Returning 0x80 + signal seems to be the standard result from a shell.
Poly/ML isn't trapping the signal. If I send "cat" a SIGKILL and then
run "echo $?" it prints 137 i.e. 0x89. Have you tried using ulimit -t
to print/adjust the time-out on the cron job?
David
_______________________________________________
polyml mailing list
[email protected]
http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
