Dear Michael,
On Sep 24, 2:25 pm, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> I don't see why 20 of those python jobs would pop up. Can you
> reproduce it?
I used nohup, and stdout was written into some file.
And I just found one detail in the log file that may help to track it
down.
It says (with my comments after "#")
Singular crashed executing def sage43815=is_fregs(sage43812,COHO1I); #
one of my Singular functions
Singular data for 625gp7 are being deleted # This message comes from
a __del__ method of my objects - see below
Singular crashed -- automatically restarting.
Singular crashed -- automatically restarting.
Singular crashed -- automatically restarting.
...
And I think this is the explanation:
- Singular crashes, so there is an error, and Sage tries to cleanly
exit.
- A clean exit means that all objects are deallocated.
- In my case, a __del__ method is called whose job it is to kill all
data (related to the object) that live in the Singular sub process.
- The sub process is dead, so a restart is attempted.
Hence, I think everything is fine on the side of Sage, but in my
__del__ method I should better test whether the Singular sub process
is still valid.
Cheers
Simon
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
