On Mon, Oct 12, 2009 at 5:20 AM, ma...@mendelu.cz <ma...@mendelu.cz> wrote: > > Hello all, I observed the following behavior of Sage 4.1.1 and 4.1.2 > rc0 > > * Sign as robert.marik > * Create worksheet > * Save & quit > * Log on > * Log in - the worksheet has been deleted > * Log on and Log in as admin --- the worksheet is stil there > > Can you reproduce this behavior at your installations of Sage? If yes, > I think that this is a bug. > > > And together with this (perhaps) bug I have another strange bahavior: > I start notebook (Sage 4.1.1) with > > notebook(address='', secure=False, accounts=True, open_viewer=False, > server_pool=['sageu...@localhost'],directory='/opt/dotsage/ > sage_notebook', timeout=2000, ulimit="-v 300000") > > and the notebooks are still running after three days. I think that > already it worked for me, but do not remember which version. Is > something broken with timeout option? Or is the problem in my computer > (virtual Debian in vmware)?
The timeout option in the released version of Sage is the *cputime*, as it is set by ulimit. So unless you are running nonstop 100% cpu computations, they won't be timed out. I don't like this behavior so in the next version of the notebook it is changed and timeout means walltime. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---