On Sat, Feb 6, 2010 at 10:11 AM, John Cremona <[email protected]> wrote: > Thanks! > > On 6 February 2010 17:22, William Stein <[email protected]> wrote: > > >>> I specifically wanted to find out which notebook was the one using >>> 15GB of ram with a maxima process! (Our algebraic geometry lecturer >> >> You might not want to allow the sage worksheet processes to use that much >> ram. >> You could put >> >> ulimit -v 1000000 >> >> to limit RAM to 1GB in that account's .bashrc and .bash_profile (make >> sure to make those files not writeable by the worksheet process >> though...). > > Instead, I could add that to the "Worksheet process limits" field in > the "Notebook settings" web page? Would that have the same effect > (i.e. on all the sever pool accounts)?
I don't think that works sufficiently robustly yes. >>> I don't know if that is a bug or not. I killed both the maxima >>> processes from the command line instead! I hope my users will not >>> mind -- in any case, I am about to stop the server and restart it >>> running 4.3.2. > > Which I just did. > >> >> That sounds like a bug. >> >> Anyway, when you restart your notebook server, you may have to >> manually login to the sage worksheet process account and kill all >> processes. The Sage notebook server only ever kills processes it >> knows about, so if anything gets left around, it'll never kill them. >> > > I did that, thanks for the hint. William -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
