#2606: command line option to kill a background notebook
---------------------------+------------------------------------------------
Reporter: nbruin | Owner: boothby
Type: enhancement | Status: new
Priority: minor | Milestone: sage-4.7
Component: notebook | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
---------------------------+------------------------------------------------
Changes (by kcrisman):
* upstream: => N/A
Old description:
> Since running sage -notebook now checks if another instance is already
> running, it would be fairly straightforward to create an option that
> kills that notebook process as well.
>
> The rationale is that it is probably much easier for a user to recreate
> the circumstances under which the notebook was started, and hence enable
> sage to find the relevant PID file, than to figure out where that PID
> file is stored.
>
> Given the code in sage.server.notebook.run_notebook it can be rather
> involved to track down where twistd.pid gets stored (and it might change
> in the future too), being able to get a hold of the pidfile in a general
> way would make startup scripts much more robust (the location of
> twistd.pid has already changed once)
>
> As an example, daemon-like services such as vncserver and dhclient have
> "-kill" and "-r" options to kill previously started instances in a way
> that takes the burden from the user to figure out which PID to kill.
>
> One should probably first address
>
> http://trac.sagemath.org/sage_trac/ticket/2359
New description:
Since running sage -notebook now checks if another instance is already
running, it would be fairly straightforward to create an option that kills
that notebook process as well.
The rationale is that it is probably much easier for a user to recreate
the circumstances under which the notebook was started, and hence enable
sage to find the relevant PID file, than to figure out where that PID file
is stored.
Given the code in sage.server.notebook.run_notebook it can be rather
involved to track down where twistd.pid gets stored (and it might change
in the future too), being able to get a hold of the pidfile in a general
way would make startup scripts much more robust (the location of
twistd.pid has already changed once)
As an example, daemon-like services such as vncserver and dhclient have
"-kill" and "-r" options to kill previously started instances in a way
that takes the burden from the user to figure out which PID to kill.
One should probably first address #2359
--
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/2606#comment:2>
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.
