On 2016-01-16 21:47, Buck Evan wrote:
It passed on subsequent `make`.
Then it might be a hardware problem. I suggest you run memtest on your
system to check for that.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this gr
PS: The Jupyter file browser jails the user into the startup directory, so
we really have to run it in $HOME
On Sunday, January 17, 2016 at 9:12:22 AM UTC+1, Volker Braun wrote:
>
> IMHO the app should just start and manage its own jupyter server; Launch
> it on startup and shut it down when
IMHO the app should just start and manage its own jupyter server; Launch it
on startup and shut it down when the app is closed. The notebook server
doesn't fork into the background so its trivial to just keep a single
process, no need for a pidfile.
If the user wants to launch a separate server
