RE: Controling dynamic memory size

[Rychlik, Marek R - (rychlik)]

Dear Jordi,
Thank you for your answer. Unfortunately, this does not help.
I do not want Octave to quit, but still do the work with less memory.
I know that my script requires minimum resources and reasonable software
should be able to run it without exhausting memory. Please look at the
option --dynamic-space-size of SBCL (Common Lisp dialect) which
solves the problem I'd like to solve. Perhaps there is a solution by
changing compile options or source code? I guess, it is about
controlling which parts of the system are loaded at start up.

Thank you.
--Marek Rychlik
Professor of Mathematics

________________________________________
From: address@hidden address@hidden On Behalf Of Jordi Gutiérrez Hermoso 
address@hidden
Sent: Monday, March 19, 2012 9:34 PM
To: Rychlik, Marek R - (rychlik)
Cc: address@hidden
Subject: Re: Controling dynamic memory size

On 19 March 2012 21:58, Rychlik, Marek R - (rychlik)
<address@hidden> wrote:
> Is there a way to impose a limit on the size of the dynamic memory allocated 
> by octave?

The jailing should be done at the OS level, not by Octave. Set
appropriate ulimits, e.g.

    https://lopsa.org/node/1755

There are many other things you want to restrict, such as fork bombs
and infinite loops. You should also run Octave in a jail, virtual
machine, or a chroot, without write permissions. These should all be
done at the OS level.

Also, it's tempting to try to disable certain Octave commands, but
this is a losing battle, because there are many ways to run
destructive Octave commands.

HTH,
- Jordi G. H.