I'm using such scheme:
1) run screen
2) run emacs into the screen sesssion
3) start shell in emacs (M+x shell)
4) run reduce
On Tuesday 19 April 2011 16:06:22 you wrote:
> Dear All,
> I'm developing reduce software for computations in the geometry of
> differential equations. The computations are quite heavy, so after 'easy'
> cases I would like to run the software on a server. This means log in into
> a server via ssh, launch the computation, logout, and then login the day
> after and see the results.
> But here I have the following problems:
> 1 - using `nohup reduce -w infile -- outfile &' does not work because (I
> guess) reduce refuses to go in background. As I try to run a computation
> in background the job stops.
> 2 - using gnu screen does not work because after I logout and login again
> the screen sessions holding reduce computations are `dead' (in screen
> terminology). screen keeps reduce working only if I do not close the ssh
> The above problems happen both with latest binaries and with 20101007
> binaries from Sourceforge, my local and remote systems are Ubuntu 64bit.
> The only thing that works is vnc; for the moment it is a good solution.
> I suspect that the above two problems have the same origin, but I have no
> clues... of course I can use vnc forever but it would be nice to know what
> is going wrong.
> Thank you very much and best wishes,
From: Martin Gregory <martin.gregory@ya...> - 2011-07-12 20:31:24
probably a naive suggestion, but why not try using at or cron? I tried
putting a call to a trivial program in a shell script, bottles.sh (don't
forget to make it executable):
and submitting with at:
$ at -m now
job 4 at Tue Jul 12 22:24:00 2011
and it created ~/reduce/bottles.out without any problems. With at or
cron there is no need to remain logged in and if you set up mail
forwarding on the server the -m option to at will tell when the job