#10187: Update ecl and maxima
------------------------------------------+---------------------------------
Reporter: vbraun | Owner: tbd
Type: defect | Status: needs_review
Priority: major | Milestone: sage-4.6.1
Component: packages | Keywords:
Author: Volker Braun, David Kirkby | Upstream: Workaround found; Bug
reported upstream.
Reviewer: Karl-Dieter Crisman | Merged:
Work_issues: |
------------------------------------------+---------------------------------
Comment(by jpflori):
Replying to [comment:85 drkirkby]:
> On a Blade 1500, you will need to increase the values of the timeouts. I
would suggest suitable values would be : ` SAGE_TIMEOUT=600
SAGE_TIMEOUT_LONG=3000 ` I suspect the SAGE_TIMEOUT_LONG could actually be
2000 seconds, but I'd go for 6000 to be really safe. I use: `
SAGE_TIMEOUT=1000 SAGE_TIMEOUT_LONG=10000 ` on a dual processor 900 MHz
Blade 1000. I think however the SAGE_TIMEOUT_LONG, which defaults to 1800
s, is probably not too far from ok, so I reckon 2000 s would be fine. The
default SAGE_TIMEOUT of 300 s will certainly be too short. Dave
I did increase the timeout, to 20000 if I remember correctly.
However when I came back Sage had gotten out of memory (and the computer
had to be restarted).
It could be because of the way I installed Sage (downloaded binary 4.5.1
package, updated the spkgs and could have used an old gcc at some point
because the default one on the system is 3.4.something even if 4.something
is available).
I should build everything from scratch but do not have the time right now.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10187#comment:87>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
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-trac?hl=en.
