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.
On Wednesday, April 25, 2018 at 12:42:54 PM UTC-7, Nils Bruin wrote: > > When you start up the jupyter notebook it writes some files describing its > state. On Fedora, they end up in in /run/user/<UID>/jupyter. There's a file > there nbserver-<PID>.json. In the file you'll find some basic data about > the server, including the "pid", which also appears in the filename. > > executing > > kill -2 <pid> > > twice in quick succession has the same result as pressing ctrl-C twice at > the terminal where the server is running, so that shuts down the notebook > cleanly. > > Obviously there can be multiple notebook servers running, even under the > same UID, so there can be multiple files there. You'll have to have a way > to pick the right one. > -- 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.
