This is about background processes in SAGE. On 2/9/07, Iftikhar Burhanuddin <[EMAIL PROTECTED]> wrote: > > On Fri, 9 Feb 2007, Timothy Clemans wrote: > > For me it is kind of annoying to have to run different servers in > > multiple terminals. Many UNIX shells support running a process in the > > background. > > > > $ command & > > $ % > > > > Would something like this be a practical to implement in SAGE? > > To run long/background computations I use nohup > > $nohup sage <file.py> output.txt & > > I also write to a file rather than print as > what-you-print-is-not-what-you-get (in output.txt) > > Regards, > Ifti > === > http://sage.math.washington.edu/home/macaulay2/sage/doc/const/node18.html > 17. Interface issues > > > 17.1 Background jobs > Yes, a SAGE job can be run in the background on a UNIX system. The > canonical thing to do is type > > nohup sage < command_file > output_file & > > The advantage of nohup is that SAGE will continue running after you log > out. > > Currently SAGE will appears as ``ipython" or ``python" in the output of > the (unix) ``top" command, but in future versions of SAGE it will appears > as ``sage". > > > > >
--~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~----------~----~----~----~------~----~------~--~---
