On Fri, Jan 23, 2009 at 5:46 PM, Dan Drake wrote:
> On Fri, 23 Jan 2009 at 01:08PM -0500, Nathan Carter wrote:
>> Yes, but I'm running it in the background (and then logging off). So
>> that process is not in the foreground anymore. (Furthermore, the sage
>> process actually starts lots of othe
On Fri, 23 Jan 2009 at 01:08PM -0500, Nathan Carter wrote:
> Yes, but I'm running it in the background (and then logging off). So
> that process is not in the foreground anymore. (Furthermore, the sage
> process actually starts lots of others, in a linear chain, so "ps ax"
> lists lots of s
This is more of a workaround than a straight answer, but you can use the
"gnu screen" terminal multiplexer to get a process started, log off, then
come back and regain console access to it. Then you can, for instance, use
ctrl-c to kill the server from within your sage session.
Best,
Alex
On Sa
Yes, but I'm running it in the background (and then logging off). So
that process is not in the foreground anymore. (Furthermore, the sage
process actually starts lots of others, in a linear chain, so "ps ax"
lists lots of sage- and sage-wiki-related stuff.)
Nathan
On Jan 23, 2009, at
Ctrl-c will shut down the server
On Fri, Jan 23, 2009 at 9:25 AM, Nathan Carter wrote:
>
>
> This may seem like a basic question, but how should I shut down the
> sage server? And the wiki? That is, I have a script that does this:
>
> /path/to/sage-3.2.3/sage start_notebook.sage &# on port
