Re: Will killing tty stop remote jobs started by that session?
- From: mechphisto@xxxxxxxxx
- Date: Wed, 11 Jun 2008 13:15:08 -0700 (PDT)
On Jun 10, 1:01 pm, mechphi...@xxxxxxxxx wrote:
On Jun 10, 12:57 pm, mechphi...@xxxxxxxxx wrote:
On my PC I've SSH'ed into a remote server and have started an rsync
that's going to take a couple of days.
I've:
# Ctrl+z && bg
to send it running in the background.
But I found that I may need to reboot my PC.
Obviously this will kill my SSH's terminal session. Will this also
kill the running job, or will it continue running until it's done
regardless of my reboot?
Thanks!
-Liam
OH, PS: That rsync is between two remote servers...not my PC. I just
started the job with my PC.
Really? No feedback?
I know the easiest way to get an answer would be for me to start a
long but harmless process on a remote system and closing the terminal
and seeing if it's still running. Case closed.
Unfortunately I can't test it as this rsync has been going for days
and still has days to go (100GB of data being transferred to a server
behind a 1Mbps connection), so IF my closing my PC's connection to the
remote server does stop the job, I REALLY don't want to have wasted
all this time.
Thanks for any reply.
.
- Follow-Ups:
- Re: Will killing tty stop remote jobs started by that session?
- From: Johan Lindquist
- Re: Will killing tty stop remote jobs started by that session?
- References:
- Will killing tty stop remote jobs started by that session?
- From: mechphisto
- Re: Will killing tty stop remote jobs started by that session?
- From: mechphisto
- Will killing tty stop remote jobs started by that session?
- Prev by Date: Re: Can someone help me?
- Next by Date: Re: Check process starting time
- Previous by thread: Re: Will killing tty stop remote jobs started by that session?
- Next by thread: Re: Will killing tty stop remote jobs started by that session?
- Index(es):
Relevant Pages
|