#6369: the sage cleaner should kill all notebook servers if sage that spawned
them
is killed
----------------------+-----------------------------------------------------
Reporter: was | Owner: boothby
Type: defect | Status: new
Priority: major | Milestone: sage-4.1
Component: notebook | Keywords:
Reviewer: | Author:
Merged: |
----------------------+-----------------------------------------------------
Description changed by was:
Old description:
> Try this:
>
> 1. {{{sage -notebook foo}}}
> 2. Find the pid of the sage -notebook process with {{{ps ax |grep "sage
> -notebook"}}}
> 3. Kill that process with {{{kill -9 [pid]}}}
> 4. The notebook server is still going. And now the only way to kill it
> is with {{{ps ax |grep tracd}}} and start killing things until you hit
> the right one.
>
> Since people, especially new sage users, often kill the notebook server
> by, e.g., clicking kill in a terminal or some other silly means, it would
> be much better if the sage-cleaner could at least step in and kill the
> notebook server, so it gets shut down cleanly (saving its state), and
> doesn't stop the notebook from running in the future (if it is always
> running, it can't run again), hence confusing users.
>
> To do all this is probably as simple as calling one little register
> function in sage.misc.cleaner.
New description:
Try this:
1. {{{sage -notebook foo}}}
2. Find the pid of the sage -notebook process with {{{ps ax |grep "sage
-notebook"}}}
3. Kill that process with {{{kill -9 [pid]}}}
4. The notebook server is still going. And now the only way to kill it
is with {{{ps ax |grep tracd}}} and start killing things until you hit the
right one.
Since people, especially new sage users, often kill the notebook server
by, e.g., clicking kill in a terminal or some other silly means, it would
be much better if the sage-cleaner could at least step in and kill the
notebook server, so it gets shut down cleanly (saving its state), and
doesn't stop the notebook from running in the future (if it is always
running, it can't run again), hence confusing users.
To do all this is probably as simple as calling one little register
function in sage.misc.cleaner.
--
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6369#comment:1>
Sage <http://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
-~----------~----~----~----~------~----~------~--~---
