I have inadvertantly got a huge rsync running in my ssh terminal session and it seems that I might kill the rsync and lose all the transfered data if I close the ssh terminal window.

Will closing the window that has the ssh session within close the ssh session itself (I believe it does) and kill the rsync that terminal is in the middle of>?

And can I background that current task or will I just have to start again and remember to use & at the endof the rsync command?

Is screen more like what I need?

TIA

Will

and then it won't kill the process when you close the session

Yes, closing the session terminates all tasks running. Using & won't alleviate this problem either, since it's still a child process of the shell. You need to use the nohup (short for "no hangup") utility to allow tasks to continue running after closing a terminal session. See the man page for details.

The screen command may also be useful. You can detach from your session and re-attach to it later. There's an overview at http://www.kuro5hin.org/story/2004/3/9/16838/14935which may be useful.

I might also do an "at" job for this type of thing.

http://www.computerhope.com/unix/uat.htm

Guys, I had problems with this last night.


I was attempting to execute an rsync that required the remote ssh login. So I put it in like

#nohup rsync [blah blah] me@remote:: &

and it accepted that and then when it asked me to accept the certificate [yes/no] and I typed yes it spooled y's down the left side of the terminal and had to be ctrl-c broken...

So I accepted the certificate separately and then re executed the command and the rsync was given a pid and then I was asked for the pass - then I got [ stopped ] and when I tried to exit the shell session I was warned of stopped tasks - I am confused now - so I left it for now!

I have managed to rsync small directories and files without hassel using a direct ssh connection and not quitting it midstream but this is ment to be the main tree backup of my remote system and I need to get the initial 2.8G of data across before the rsync size and session length becomes trivial. Help anyone? Many Thansk

will

Why don't you try pulling the data to your machine instead of pushing it from the other? That is, say the machine you want the files from is OVERTHERE, and the one you're at is HERE. Right now you're sshing OVERTHERE and then:

Instead you can just rsync from HERE, like this:

You d'man!

That has got it sorted. I am easily pulling 200kps and the job looks like taking 4 hours instead of 59 and then stalling and aborting! Thanks heaps>