Nope -- or at least, not for me. "jupyter notebook list" works fine, but
"jupyter notebook stop " 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 jupyt
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
> assumpt
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
When you start up the jupyter notebook it writes some files describing its
state. On Fedora, they end up in in /run/user//jupyter. There's a file
there nbserver-.json. In the file you'll find some basic data about
the server, including the "pid", which also appears in the filename.
executing
k
