On Dec 3, 10:59 am, kcrisman <[EMAIL PROTECTED]> wrote: Hi,
> Just wanted to follow up on this for the collective good... Yep, that seems like a good idea. <SNIP> > > c) could easily. Did you set the timeout parameter for the server? > > > timeout -- (default: 0) seconds until idle worksheet sessions > > automatically timeout, i.e., the corresponding > > Sage session terminates. 0 means 'never > > timeout'. > > That seems to have been the other main problem, and we fixed it. Care to open a ticket to update the docstring? I think it would be good to mention that on low memory systems one should set some timeout since otherwise Sage will gobble up all available memory if there are many users. > So now I have a healthy class of 30 students successfully using Sage > to explore chaos in calculus! They sometimes get slowdowns when there > are a number of them on it, but never the total logout except when a > local switch is broken, which is of course not Sage-related. Even > under quite constrained conditions, it seems to be working quite > nicely. Imagine how well a Sage lite would work ;) > > Thanks, > - kcrisman Cheers, Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
