Opened 15 years ago

Closed 13 years ago

Last modified 13 years ago

#2518 closed defect (invalid)

improve the SAGE_ROOT/local/bin/sage-cleaner script so that it kills those damn lisp.run processes

Reported by: was Owned by: mabshoff
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: misc Keywords:
Cc: was, mhansen, robertwb Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

GitHub link to the corresponding issue

Description

Fact is, several people have observed lisp.run's getting left running.

If *anybody* can find a 100% reliable way to replicate this problem, PLEASE LET US KNOW!

Change History (4)

comment:1 Changed 15 years ago by mabshoff

Owner: changed from cwitty to mabshoff
Status: new → assigned

The issue here is likely that we use 

os.kill(int(pid),0)

It is likely that using "kill -9 $PID" via os.system() ought to fix the issue.

Cheers,

Michael

comment:2 Changed 14 years ago by mabshoff

I believe the problem was that if clisp crashed and restarted those processes could get stuck at 99% and not be killed at exit.

This hasn't been reported in a while, so I would prefer to close this as fixed. Thoughts?

Cheers,

Michael

comment:3 Changed 13 years ago by timdumol

Cc: was mhansen robertwb added
Report Upstream: → N/A
Resolution: → fixed
Status: new → closed

Since this hasn't been reported in around 8 months, I think this should be closed.

comment:4 Changed 13 years ago by mhansen

Milestone: sage-4.3.1 → sage-duplicate/invalid/wontfix
Resolution: fixed → invalid

Seems reasonable to me.

Note: See TracTickets for help on using tickets.