[Gllug] Re-access broken remote connection to process?

[James Courtier-Dutton]

On 18 June 2010 06:30, JLMS <jjllmmss at googlemail.com> wrote:
> On Thu, Jun 17, 2010 at 11:07 PM, tid <td at bloogaloo.co.uk> wrote:
>> I've seen a few situations where people tied themselves in knots by
>> staying late at the office 'because I can't afford to let this process die
>> if the
>> net connection dies' or implemented ssh keepalives via ping which were
>> sorted
>> by screen and/or nohup
>>
>> also, another useful command is 'watch'.
>>
>> tid
>
> There are terminal servers that kick you out after a period of
> "inactivity" in situations in which you can't use screen, and for
> which building expect scripts would be too time consuming.
>
> I have been paid a daily rate just to baby sit long processes running
> on those circumstances.... (the joy)....
> --

If it is a long job, it should really have been programmed to work as
a batch job.
Here you run it in the background and once it has finished, you get an
email with all the text output from it.

Another thing I often do is run a command like this:

rsync -av x y >t1 2>t2 &

This will run the program in the background and save all the output in
two text files.
I also use nx and screen when the need requires it.
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug