Re: Continuous running (was Re: gnuclient *feature* -- crash when frames lose X connection)
Samuel Mikes writes:
>> In particular, what I'm aiming for is for XEmacs to keep running
>> on my unix box when my Windows box crashes, killing my ssh
>> sessions. Once I'm back up, ideally I would ssh back in, run
>> gnuclient -nw, and reconnect to my running XEmacs, not having to
>> recover various VM and BBDB buffers.
i mentioned screen in a previous post, but i was vague...
as i have problems similar to yours, and having this recollection of
screen being the/one solution, i tried to read screen's man page, and
all the pieces came to my mind
here is my recipe: please note that it's not as convenient as
gnuclient, and you have to type C-a a in place of a single C-a, as
screen use C-a as its escape character, but i can do as follows
local% [connect to some provider ＠56kbs]&
local% ssh gb(a)somehost.somewhere
remote# screen xemacs -nw
......
......
[the connection is abrubtly down:
i had to type the ssh escape "RET ~." to go back to my PC]
local% [re-connect to the same lousy (but extremely cheap :-) provider]&
local% ssh gb(a)somehost.somewhere
remote# screen -r
......
[back in xemacs exactly where i was when the connection was broken]
......
C-a d [this command detaches the screen session from the terminal]
remote# exit [note that xemacs still runs in the detached session]
local%