Nope -- or at least, not for me. "jupyter notebook list" works fine, but "jupyter notebook stop 8888" returns an error indicating that the file stop can not be found... Perhaps this feature has been dropped? This approach also appears to be slow, presumably due to overhead when starting jupyter.
On Thursday, May 3, 2018 at 2:47:51 PM UTC-7, Nils Bruin wrote: > > On Thursday, May 3, 2018 at 2:32:22 PM UTC-7, Tevian Dray wrote: >> >> Finally had a chance to test this; yes it works -- although it is >> apparently possible to send the two kill commands too close together. Thank >> you very much. Have to say it's a bit of a kluge, though -- the design >> assumption that notebooks will always be started in shell windows that stay >> open is surely flawed. >> >> Indeed, there seems to be an even righter way: > > https://github.com/jupyter/notebook/issues/1950 > > apparently you can do > > $ jupyter notebook list > <you will see port number> > $ jupyter notebook stop <port number> > > When doing this with sage you'd have to make sure to run it through sage's > jupyter, so something like > > $ sage -sh -c "jupyter notebook list" > $ sage -sh -c "jupyter notebook stop <port number>" > > > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
