On Jul 7, 3:52 pm, William Stein <[email protected]> wrote:
> On Tue, Jul 7, 2009 at 12:29 PM, Ethan Van Andel<[email protected]> wrote:
>
> > I am running some image generation stuff over the sagenb server. They
> > can take a LONG time (2.5 hours or more). I find that often when I
> > check on the process, it has been interupted with an error message
> > like this:
>
> > /home/sage/sage_install/sage/local/bin/sage-sage: line 349: 3500
> > Killed
> > python "$@"
> > Connection to localhost closed.
>
> > What is causing this? If it's an automatic killing of processes that
> > run too long that the server thinks that they're stuck, is there some
> > sort of "don't kill me, I know what I'm doing" flag that I can use to
> > protect my process?
>
> Yes. All processes on the public sagenb.org server are automatically
> killed after about an hour of CPU time. If you want to run much
> longer computations, you'll have to use a less public resource.
> (E.g., contact me offlist and we can "work something out".)
>
> -- William
Thanks for the info. I should have more local computing power shortly,
so that shouldn't be a problem.
Ethan
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---
