Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

How can I pause an rsync that's running?

First time I did Ctrl+C to kill it and used the -P flag to run again. Is this prone to corrupt the current file transfer?

Second time I simply put MacOS to sleep (by closing the lid). Looking at the running process I can see 2 (not sure why) with a status of 'S'.

Tried using


to resume the process, but it has no effect.

share|improve this question
up vote 43 down vote accepted

You can pause any program by sending it a TSTP (polite) or STOP (forcible) signal. On the terminal you've run rsync in, pressing Ctrl+Z sends TSTP. Resume with the fg or bg command in the terminal or a CONT signal.

It is safe to kill an rsync process and run the whole thing again; it will continue where it left off. It may be a little inefficient, particularly if you haven't passed --partial (included in -P), because rsync will check all files again and process the file it was interrupted on from scratch.

There may be unusual combinations of options that will lead to some files not being synchronized properly, maybe --inplace with something else, but I think no single option will cause this.

If you disconnect your laptop and reconnect it somewhere else, it may get a different IP address. Then the TCP connection used by rsync would be severed, so you'd have to kill it and start again. This can also happen if you suspend your laptop and the TCP connection times out. The timeout will eventually filter out to the application level, but it can take a while. It's safe to press Ctrl+C and run rsync again.

share|improve this answer
Actually killing rsync -avh simply loose the current file being copied, if the file is large you've lost quite a lot of time. Maybe Ctrl+z moving the temporary file (start with a dot) and then Ctrl-C rsync might be a better solution. – malat Oct 1 '14 at 8:49
Thanks for such a detailed explanation. To clarify: ctrl+z to pause, fg to resume, bg to stop. – Praesagus Oct 30 '15 at 16:20
@Praesagus bg to put process to the background, not to stop. – koiyu Jul 3 at 19:14

Ctrl+Z to suspend, and:

$ fg

to continue, use

$ jobs

to see suspended jobs; bg [number] to background them; fg [number] to foreground it.

share|improve this answer
Ctrl+S only suspends scrolling output, not the underlying program (unless it gets blocked waiting for the terminal to accept its output), and only if you haven't disabled it. – Gilles Jan 16 '11 at 13:31
With the current 'S' status it doesn't resume. Is it safe to kill it using Ctrl+C and run rsync again? What other options do I have? Will have that in mind next time though, thanks. – qnoid Jan 16 '11 at 13:32
Also note that Ctrl-Z to suspend a process is likely, after some time, to result in the timeout of any TCP network connections which were established by that program. Thus leaving an rsync suspended for more than a few minutes will very likely cause it to quit abruptly with an error message when you put it back in the foreground and it finds that its opened sockets are returning errors from reads and writes. – Jim Dennis Jan 17 '11 at 14:18

Run rsync with the --partial flag. It will then keep partial transfers and resume partial files when started.

share|improve this answer

People here have mentioned using the --partial flag works, it needs to be mentioned however that it only resumes when the --append or --append-verify flag is used when resuming.

--partial creates a hidden file of the file that has not finished the sync process, the file is kept when you interrupt syncing. It continues to complete the file when you use --append after resuming, otherwise when not using --append, the incomplete hidden file is kept and remains incomplete.

Conclusion: You can just interrupt rsync --partial using Ctrl + C if you use rsync --append when resuming

(Source: Can rsync resume after being interrupted? retrieved 5 april 2016)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.