Commit | Line | Data |
---|---|---|
9e3c856a | 1 | mailto(rsync-bugs@samba.org) |
618c8a73 | 2 | manpage(rsync)(1)(30 Sep 2004)()() |
41059f75 AT |
3 | manpagename(rsync)(faster, flexible replacement for rcp) |
4 | manpagesynopsis() | |
5 | ||
9ef53907 | 6 | rsync [OPTION]... SRC [SRC]... [USER@]HOST:DEST |
41059f75 | 7 | |
9ef53907 | 8 | rsync [OPTION]... [USER@]HOST:SRC DEST |
41059f75 | 9 | |
9ef53907 | 10 | rsync [OPTION]... SRC [SRC]... DEST |
41059f75 | 11 | |
9ef53907 | 12 | rsync [OPTION]... [USER@]HOST::SRC [DEST] |
41059f75 | 13 | |
9ef53907 | 14 | rsync [OPTION]... SRC [SRC]... [USER@]HOST::DEST |
41059f75 | 15 | |
9ef53907 | 16 | rsync [OPTION]... rsync://[USER@]HOST[:PORT]/SRC [DEST] |
039faa86 | 17 | |
8d69d571 WD |
18 | rsync [OPTION]... SRC [SRC]... rsync://[USER@]HOST[:PORT]/DEST |
19 | ||
41059f75 AT |
20 | manpagedescription() |
21 | ||
22 | rsync is a program that behaves in much the same way that rcp does, | |
23 | but has many more options and uses the rsync remote-update protocol to | |
675ef1aa WD |
24 | greatly speed up file transfers when the destination file is being |
25 | updated. | |
41059f75 AT |
26 | |
27 | The rsync remote-update protocol allows rsync to transfer just the | |
f39281ae | 28 | differences between two sets of files across the network connection, using |
41059f75 AT |
29 | an efficient checksum-search algorithm described in the technical |
30 | report that accompanies this package. | |
31 | ||
32 | Some of the additional features of rsync are: | |
33 | ||
34 | itemize( | |
b9f592fb | 35 | it() support for copying links, devices, owners, groups, and permissions |
41059f75 AT |
36 | it() exclude and exclude-from options similar to GNU tar |
37 | it() a CVS exclude mode for ignoring the same files that CVS would ignore | |
43cd760f | 38 | it() can use any transparent remote shell, including ssh or rsh |
41059f75 AT |
39 | it() does not require root privileges |
40 | it() pipelining of file transfers to minimize latency costs | |
41 | it() support for anonymous or authenticated rsync servers (ideal for | |
42 | mirroring) | |
43 | ) | |
44 | ||
45 | manpagesection(GENERAL) | |
46 | ||
bef49340 | 47 | There are eight different ways of using rsync. They are: |
41059f75 AT |
48 | |
49 | itemize( | |
50 | it() for copying local files. This is invoked when neither | |
51 | source nor destination path contains a : separator | |
52 | ||
53 | it() for copying from the local machine to a remote machine using | |
43cd760f WD |
54 | a remote shell program as the transport (such as ssh or |
55 | rsh). This is invoked when the destination path contains a | |
41059f75 AT |
56 | single : separator. |
57 | ||
58 | it() for copying from a remote machine to the local machine | |
6c7c2ef3 | 59 | using a remote shell program. This is invoked when the source |
41059f75 AT |
60 | contains a : separator. |
61 | ||
62 | it() for copying from a remote rsync server to the local | |
63 | machine. This is invoked when the source path contains a :: | |
bb18e755 | 64 | separator or an rsync:// URL. |
41059f75 AT |
65 | |
66 | it() for copying from the local machine to a remote rsync | |
67 | server. This is invoked when the destination path contains a :: | |
bb18e755 | 68 | separator or an rsync:// URL. |
039faa86 | 69 | |
bef49340 WD |
70 | it() for copying from a remote machine using a remote shell |
71 | program as the transport, using rsync server on the remote | |
72 | machine. This is invoked when the source path contains a :: | |
73 | separator and the --rsh=COMMAND (aka "-e COMMAND") option is | |
74 | also provided. | |
75 | ||
76 | it() for copying from the local machine to a remote machine | |
77 | using a remote shell program as the transport, using rsync | |
78 | server on the remote machine. This is invoked when the | |
79 | destination path contains a :: separator and the | |
4d888108 | 80 | --rsh=COMMAND option is also provided. |
bef49340 | 81 | |
039faa86 AT |
82 | it() for listing files on a remote machine. This is done the |
83 | same way as rsync transfers except that you leave off the | |
84 | local destination. | |
41059f75 AT |
85 | ) |
86 | ||
14d43f1f DD |
87 | Note that in all cases (other than listing) at least one of the source |
88 | and destination paths must be local. | |
41059f75 AT |
89 | |
90 | manpagesection(SETUP) | |
91 | ||
92 | See the file README for installation instructions. | |
93 | ||
1bbf83c0 WD |
94 | Once installed, you can use rsync to any machine that you can access via |
95 | a remote shell (as well as some that you can access using the rsync | |
43cd760f | 96 | daemon-mode protocol). For remote transfers, a modern rsync uses ssh |
1bbf83c0 | 97 | for its communications, but it may have been configured to use a |
43cd760f | 98 | different remote shell by default, such as rsh or remsh. |
41059f75 | 99 | |
1bbf83c0 | 100 | You can also specify any remote shell you like, either by using the -e |
41059f75 AT |
101 | command line option, or by setting the RSYNC_RSH environment variable. |
102 | ||
103 | One common substitute is to use ssh, which offers a high degree of | |
104 | security. | |
105 | ||
8e987130 AT |
106 | Note that rsync must be installed on both the source and destination |
107 | machines. | |
108 | ||
41059f75 AT |
109 | manpagesection(USAGE) |
110 | ||
111 | You use rsync in the same way you use rcp. You must specify a source | |
112 | and a destination, one of which may be remote. | |
113 | ||
4d888108 | 114 | Perhaps the best way to explain the syntax is with some examples: |
41059f75 | 115 | |
675ef1aa | 116 | quote(rsync -t *.c foo:src/) |
41059f75 | 117 | |
8a97fc2e | 118 | This would transfer all files matching the pattern *.c from the |
41059f75 AT |
119 | current directory to the directory src on the machine foo. If any of |
120 | the files already exist on the remote system then the rsync | |
121 | remote-update protocol is used to update the file by sending only the | |
122 | differences. See the tech report for details. | |
123 | ||
124 | quote(rsync -avz foo:src/bar /data/tmp) | |
125 | ||
8a97fc2e | 126 | This would recursively transfer all files from the directory src/bar on the |
41059f75 AT |
127 | machine foo into the /data/tmp/bar directory on the local machine. The |
128 | files are transferred in "archive" mode, which ensures that symbolic | |
b5accaba | 129 | links, devices, attributes, permissions, ownerships, etc. are preserved |
14d43f1f | 130 | in the transfer. Additionally, compression will be used to reduce the |
41059f75 AT |
131 | size of data portions of the transfer. |
132 | ||
133 | quote(rsync -avz foo:src/bar/ /data/tmp) | |
134 | ||
8a97fc2e WD |
135 | A trailing slash on the source changes this behavior to avoid creating an |
136 | additional directory level at the destination. You can think of a trailing | |
137 | / on a source as meaning "copy the contents of this directory" as opposed | |
138 | to "copy the directory by name", but in both cases the attributes of the | |
139 | containing directory are transferred to the containing directory on the | |
140 | destination. In other words, each of the following commands copies the | |
141 | files in the same way, including their setting of the attributes of | |
142 | /dest/foo: | |
143 | ||
675ef1aa WD |
144 | quote(rsync -av /src/foo /dest) |
145 | quote(rsync -av /src/foo/ /dest/foo) | |
41059f75 AT |
146 | |
147 | You can also use rsync in local-only mode, where both the source and | |
148 | destination don't have a ':' in the name. In this case it behaves like | |
149 | an improved copy command. | |
150 | ||
14d43f1f DD |
151 | quote(rsync somehost.mydomain.com::) |
152 | ||
8a97fc2e | 153 | This would list all the anonymous rsync modules available on the host |
14d43f1f DD |
154 | somehost.mydomain.com. (See the following section for more details.) |
155 | ||
41059f75 | 156 | |
675ef1aa WD |
157 | manpagesection(ADVANCED USAGE) |
158 | ||
159 | The syntax for requesting multiple files from a remote host involves using | |
160 | quoted spaces in the SRC. Some examples: | |
161 | ||
162 | quote(rsync host::'modname/dir1/file1 modname/dir2/file2' /dest) | |
163 | ||
164 | This would copy file1 and file2 into /dest from an rsync daemon. Each | |
165 | additional arg must include the same "modname/" prefix as the first one, | |
166 | and must be preceded by a single space. All other spaces are assumed | |
167 | to be a part of the filenames. | |
168 | ||
169 | quote(rsync -av host:'dir1/file1 dir2/file2' /dest) | |
170 | ||
171 | This would copy file1 and file2 into /dest using a remote shell. This | |
172 | word-splitting is done by the remote shell, so if it doesn't work it means | |
173 | that the remote shell isn't configured to split its args based on | |
174 | whitespace (a very rare setting, but not unknown). If you need to transfer | |
175 | a filename that contains whitespace, you'll need to either escape the | |
176 | whitespace in a way that the remote shell will understand, or use wildcards | |
177 | in place of the spaces. Two examples of this are: | |
178 | ||
179 | quote(rsync -av host:'file\ name\ with\ spaces' /dest) | |
180 | quote(rsync -av host:file?name?with?spaces /dest) | |
181 | ||
182 | This latter example assumes that your shell passes through unmatched | |
183 | wildcards. If it complains about "no match", put the name in quotes. | |
184 | ||
185 | ||
41059f75 AT |
186 | manpagesection(CONNECTING TO AN RSYNC SERVER) |
187 | ||
1bbf83c0 | 188 | It is also possible to use rsync without a remote shell as the |
41059f75 AT |
189 | transport. In this case you will connect to a remote rsync server |
190 | running on TCP port 873. | |
191 | ||
eb06fa95 | 192 | You may establish the connection via a web proxy by setting the |
4c3b4b25 | 193 | environment variable RSYNC_PROXY to a hostname:port pair pointing to |
4d888108 WD |
194 | your web proxy. Note that your web proxy's configuration must support |
195 | proxy connections to port 873. | |
4c3b4b25 | 196 | |
1bbf83c0 | 197 | Using rsync in this way is the same as using it with a remote shell except |
41059f75 AT |
198 | that: |
199 | ||
200 | itemize( | |
201 | it() you use a double colon :: instead of a single colon to | |
bb18e755 | 202 | separate the hostname from the path or an rsync:// URL. |
41059f75 AT |
203 | |
204 | it() the remote server may print a message of the day when you | |
14d43f1f | 205 | connect. |
41059f75 AT |
206 | |
207 | it() if you specify no path name on the remote server then the | |
208 | list of accessible paths on the server will be shown. | |
14d43f1f | 209 | |
f7632fc6 | 210 | it() if you specify no local destination then a listing of the |
14d43f1f | 211 | specified files on the remote server is provided. |
41059f75 AT |
212 | ) |
213 | ||
4c3d16be AT |
214 | Some paths on the remote server may require authentication. If so then |
215 | you will receive a password prompt when you connect. You can avoid the | |
216 | password prompt by setting the environment variable RSYNC_PASSWORD to | |
65575e96 AT |
217 | the password you want to use or using the --password-file option. This |
218 | may be useful when scripting rsync. | |
4c3d16be | 219 | |
3bc67f0c | 220 | WARNING: On some systems environment variables are visible to all |
65575e96 | 221 | users. On those systems using --password-file is recommended. |
3bc67f0c | 222 | |
bef49340 WD |
223 | manpagesection(CONNECTING TO AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM) |
224 | ||
225 | It is sometimes useful to be able to set up file transfers using rsync | |
43cd760f WD |
226 | server capabilities on the remote machine, while still using ssh or |
227 | rsh for transport. This is especially useful when you want to connect | |
bef49340 WD |
228 | to a remote machine via ssh (for encryption or to get through a |
229 | firewall), but you still want to have access to the rsync server | |
230 | features (see RUNNING AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM, | |
231 | below). | |
232 | ||
233 | From the user's perspective, using rsync in this way is the same as | |
234 | using it to connect to an rsync server, except that you must | |
235 | explicitly set the remote shell program on the command line with | |
236 | --rsh=COMMAND. (Setting RSYNC_RSH in the environment will not turn on | |
237 | this functionality.) | |
238 | ||
239 | In order to distinguish between the remote-shell user and the rsync | |
240 | server user, you can use '-l user' on your remote-shell command: | |
241 | ||
242 | quote(rsync -av --rsh="ssh -l ssh-user" rsync-user@host::module[/path] local-path) | |
243 | ||
244 | The "ssh-user" will be used at the ssh level; the "rsync-user" will be | |
245 | used to check against the rsyncd.conf on the remote host. | |
246 | ||
41059f75 AT |
247 | manpagesection(RUNNING AN RSYNC SERVER) |
248 | ||
4d888108 | 249 | An rsync server is configured using a configuration file. Please see the |
30e8c8e1 DD |
250 | rsyncd.conf(5) man page for more information. By default the configuration |
251 | file is called /etc/rsyncd.conf, unless rsync is running over a remote | |
252 | shell program and is not running as root; in that case, the default name | |
253 | is rsyncd.conf in the current directory on the remote computer | |
254 | (typically $HOME). | |
41059f75 | 255 | |
bef49340 WD |
256 | manpagesection(RUNNING AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM) |
257 | ||
258 | See the rsyncd.conf(5) man page for full information on the rsync | |
259 | server configuration file. | |
260 | ||
261 | Several configuration options will not be available unless the remote | |
262 | user is root (e.g. chroot, setuid/setgid, etc.). There is no need to | |
263 | configure inetd or the services map to include the rsync server port | |
264 | if you run an rsync server only via a remote shell program. | |
265 | ||
e6f9e388 WD |
266 | To run an rsync server out of a single-use ssh key, see this section |
267 | in the rsyncd.conf(5) man page. | |
bef49340 | 268 | |
41059f75 AT |
269 | manpagesection(EXAMPLES) |
270 | ||
271 | Here are some examples of how I use rsync. | |
272 | ||
14d43f1f DD |
273 | To backup my wife's home directory, which consists of large MS Word |
274 | files and mail folders, I use a cron job that runs | |
41059f75 AT |
275 | |
276 | quote(rsync -Cavz . arvidsjaur:backup) | |
277 | ||
f39281ae | 278 | each night over a PPP connection to a duplicate directory on my machine |
41059f75 AT |
279 | "arvidsjaur". |
280 | ||
281 | To synchronize my samba source trees I use the following Makefile | |
282 | targets: | |
283 | ||
284 | quote( get:nl() | |
285 | rsync -avuzb --exclude '*~' samba:samba/ . | |
286 | ||
287 | put:nl() | |
288 | rsync -Cavuzb . samba:samba/ | |
289 | ||
290 | sync: get put) | |
291 | ||
292 | this allows me to sync with a CVS directory at the other end of the | |
f39281ae | 293 | connection. I then do cvs operations on the remote machine, which saves a |
41059f75 AT |
294 | lot of time as the remote cvs protocol isn't very efficient. |
295 | ||
296 | I mirror a directory between my "old" and "new" ftp sites with the | |
297 | command | |
298 | ||
299 | quote(rsync -az -e ssh --delete ~ftp/pub/samba/ nimbus:"~ftp/pub/tridge/samba") | |
300 | ||
301 | this is launched from cron every few hours. | |
302 | ||
c95da96a AT |
303 | manpagesection(OPTIONS SUMMARY) |
304 | ||
14d43f1f | 305 | Here is a short summary of the options available in rsync. Please refer |
c95da96a AT |
306 | to the detailed description below for a complete description. |
307 | ||
308 | verb( | |
309 | -v, --verbose increase verbosity | |
44d98d61 | 310 | -q, --quiet suppress non-error messages |
c95da96a | 311 | -c, --checksum always checksum |
44d98d61 WD |
312 | -c, --checksum skip based on checksum, not mod-time & size |
313 | -a, --archive archive mode; same as -rlptgoD (no -H) | |
c95da96a AT |
314 | -r, --recursive recurse into directories |
315 | -R, --relative use relative path names | |
f177b7cc WD |
316 | --no-relative turn off --relative |
317 | --no-implied-dirs don't send implied dirs with -R | |
915dd207 | 318 | -b, --backup make backups (see --suffix & --backup-dir) |
44d98d61 | 319 | --backup-dir=DIR make backups into hierarchy based in DIR |
915dd207 | 320 | --suffix=SUFFIX backup suffix (default ~ w/o --backup-dir) |
44d98d61 WD |
321 | -u, --update skip files that are newer on the receiver |
322 | --inplace update destination files in-place | |
09ed3099 | 323 | -d, --dirs transfer directories without recursing |
eb06fa95 | 324 | -l, --links copy symlinks as symlinks |
44d98d61 WD |
325 | -L, --copy-links transform symlink into referent file/dir |
326 | --copy-unsafe-links only "unsafe" symlinks are transformed | |
327 | --safe-links ignore symlinks that point outside the tree | |
c95da96a | 328 | -H, --hard-links preserve hard links |
09ed3099 | 329 | -K, --keep-dirlinks treat symlinked dir on receiver as dir |
c95da96a AT |
330 | -p, --perms preserve permissions |
331 | -o, --owner preserve owner (root only) | |
332 | -g, --group preserve group | |
333 | -D, --devices preserve devices (root only) | |
334 | -t, --times preserve times | |
54e66f1d | 335 | -O, --omit-dir-times omit directories when preserving times |
c95da96a AT |
336 | -S, --sparse handle sparse files efficiently |
337 | -n, --dry-run show what would have been transferred | |
44d98d61 WD |
338 | -W, --whole-file copy files whole |
339 | --no-whole-file always use incremental rsync algorithm | |
c95da96a | 340 | -x, --one-file-system don't cross filesystem boundaries |
3ed8eb3f | 341 | -B, --block-size=SIZE force a fixed checksum block-size |
44d98d61 | 342 | -e, --rsh=COMMAND specify the remote shell to use |
d9fcc198 | 343 | --rsync-path=PATH specify path to rsync on the remote machine |
1347d512 | 344 | --existing only update files that already exist |
915dd207 | 345 | --ignore-existing ignore files that already exist on receiver |
ae76a740 | 346 | --del an alias for --delete-during |
915dd207 | 347 | --delete delete files that don't exist on sender |
598c409e | 348 | --delete-before receiver deletes before transfer (default) |
ae76a740 WD |
349 | --delete-during receiver deletes during xfer, not before |
350 | --delete-after receiver deletes after transfer, not before | |
866925bf | 351 | --delete-excluded also delete excluded files on receiver |
b5accaba | 352 | --ignore-errors delete even if there are I/O errors |
866925bf | 353 | --force force deletion of dirs even if not empty |
0b73ca12 | 354 | --max-delete=NUM don't delete more than NUM files |
3610c458 | 355 | --max-size=SIZE don't transfer any file larger than SIZE |
c95da96a | 356 | --partial keep partially transferred files |
44cad59f | 357 | --partial-dir=DIR put a partially transferred file into DIR |
44d98d61 | 358 | --delay-updates put all updated files into place at end |
c95da96a | 359 | --numeric-ids don't map uid/gid values by user/group name |
b5accaba | 360 | --timeout=TIME set I/O timeout in seconds |
44d98d61 WD |
361 | -I, --ignore-times don't skip files that match size and time |
362 | --size-only skip files that match in size | |
363 | --modify-window=NUM compare mod-times with reduced accuracy | |
c95da96a | 364 | -T --temp-dir=DIR create temporary files in directory DIR |
915dd207 | 365 | --compare-dest=DIR also compare received files relative to DIR |
b127c1dc WD |
366 | --copy-dest=DIR ... and include copies of unchanged files |
367 | --link-dest=DIR hardlink to files in DIR when unchanged | |
c95da96a | 368 | -z, --compress compress file data |
44d98d61 | 369 | -C, --cvs-exclude auto-ignore files in the same way CVS does |
16e5de84 WD |
370 | -f, --filter=RULE add a file-filtering RULE |
371 | -F same as --filter=': /.rsync-filter' | |
372 | repeated: --filter='- .rsync-filter' | |
2acf81eb | 373 | --exclude=PATTERN exclude files matching PATTERN |
44d98d61 | 374 | --exclude-from=FILE read exclude patterns from FILE |
2acf81eb | 375 | --include=PATTERN don't exclude files matching PATTERN |
44d98d61 WD |
376 | --include-from=FILE read include patterns from FILE |
377 | --files-from=FILE read list of source-file names from FILE | |
378 | -0 --from0 all *from file lists are delimited by nulls | |
c95da96a | 379 | --version print version number |
c259892c | 380 | --port=PORT specify double-colon alternate port number |
b5accaba | 381 | --blocking-io use blocking I/O for the remote shell |
44d98d61 WD |
382 | --no-blocking-io turn off blocking I/O when it is default |
383 | --stats give some file-transfer stats | |
eb86d661 | 384 | --progress show progress during transfer |
44d98d61 WD |
385 | -P same as --partial --progress |
386 | --log-format=FORMAT log file-transfers using specified format | |
387 | --password-file=FILE read password from FILE | |
09ed3099 | 388 | --list-only list the files instead of copying them |
44d98d61 WD |
389 | --bwlimit=KBPS limit I/O bandwidth; KBytes per second |
390 | --write-batch=FILE write a batched update to FILE | |
391 | --read-batch=FILE read a batched update from FILE | |
392 | --checksum-seed=NUM set block/file checksum seed (advanced) | |
e40a46de WD |
393 | -4 --ipv4 prefer IPv4 |
394 | -6 --ipv6 prefer IPv6 | |
c95da96a | 395 | -h, --help show this help screen |
bdf278f7 | 396 | ) |
6902ed17 | 397 | |
bdf278f7 | 398 | Rsync can also be run as a daemon, in which case the following options are accepted: |
6902ed17 | 399 | |
bdf278f7 WD |
400 | verb( |
401 | --daemon run as an rsync daemon | |
402 | --address=ADDRESS bind to the specified address | |
44d98d61 | 403 | --bwlimit=KBPS limit I/O bandwidth; KBytes per second |
bdf278f7 WD |
404 | --config=FILE specify alternate rsyncd.conf file |
405 | --no-detach do not detach from the parent | |
c259892c | 406 | --port=PORT listen on alternate port number |
24b0922b | 407 | -v, --verbose increase verbosity |
bdf278f7 WD |
408 | -4 --ipv4 prefer IPv4 |
409 | -6 --ipv6 prefer IPv6 | |
410 | -h, --help show this help screen | |
c95da96a AT |
411 | ) |
412 | ||
41059f75 AT |
413 | manpageoptions() |
414 | ||
415 | rsync uses the GNU long options package. Many of the command line | |
416 | options have two variants, one short and one long. These are shown | |
14d43f1f | 417 | below, separated by commas. Some options only have a long variant. |
b5679335 DD |
418 | The '=' for options that take a parameter is optional; whitespace |
419 | can be used instead. | |
41059f75 AT |
420 | |
421 | startdit() | |
422 | dit(bf(-h, --help)) Print a short help page describing the options | |
bdf278f7 | 423 | available in rsync. |
41059f75 | 424 | |
bdf278f7 | 425 | dit(bf(--version)) print the rsync version number and exit. |
41059f75 AT |
426 | |
427 | dit(bf(-v, --verbose)) This option increases the amount of information you | |
14d43f1f | 428 | are given during the transfer. By default, rsync works silently. A |
41059f75 AT |
429 | single -v will give you information about what files are being |
430 | transferred and a brief summary at the end. Two -v flags will give you | |
431 | information on what files are being skipped and slightly more | |
432 | information at the end. More than two -v flags should only be used if | |
14d43f1f | 433 | you are debugging rsync. |
41059f75 | 434 | |
b86f0cef DD |
435 | dit(bf(-q, --quiet)) This option decreases the amount of information you |
436 | are given during the transfer, notably suppressing information messages | |
437 | from the remote server. This flag is useful when invoking rsync from | |
438 | cron. | |
439 | ||
41059f75 | 440 | dit(bf(-I, --ignore-times)) Normally rsync will skip any files that are |
915dd207 WD |
441 | already the same size and have the same modification time-stamp. |
442 | This option turns off this "quick check" behavior. | |
41059f75 | 443 | |
a03a9f4e | 444 | dit(bf(--size-only)) Normally rsync will not transfer any files that are |
915dd207 | 445 | already the same size and have the same modification time-stamp. With the |
a03a9f4e | 446 | --size-only option, files will not be transferred if they have the same size, |
f83f0548 AT |
447 | regardless of timestamp. This is useful when starting to use rsync |
448 | after using another mirroring system which may not preserve timestamps | |
449 | exactly. | |
450 | ||
5b56cc19 AT |
451 | dit(bf(--modify-window)) When comparing two timestamps rsync treats |
452 | the timestamps as being equal if they are within the value of | |
453 | modify_window. This is normally zero, but you may find it useful to | |
454 | set this to a larger value in some situations. In particular, when | |
38843171 DD |
455 | transferring to Windows FAT filesystems which cannot represent times |
456 | with a 1 second resolution --modify-window=1 is useful. | |
5b56cc19 | 457 | |
41059f75 AT |
458 | dit(bf(-c, --checksum)) This forces the sender to checksum all files using |
459 | a 128-bit MD4 checksum before transfer. The checksum is then | |
460 | explicitly checked on the receiver and any files of the same name | |
461 | which already exist and have the same checksum and size on the | |
a03a9f4e | 462 | receiver are not transferred. This option can be quite slow. |
41059f75 | 463 | |
e7bf3e5e MP |
464 | dit(bf(-a, --archive)) This is equivalent to -rlptgoD. It is a quick |
465 | way of saying you want recursion and want to preserve almost | |
466 | everything. | |
467 | ||
468 | Note however that bf(-a) bf(does not preserve hardlinks), because | |
469 | finding multiply-linked files is expensive. You must separately | |
470 | specify bf(-H). | |
41059f75 | 471 | |
24986abd | 472 | dit(bf(-r, --recursive)) This tells rsync to copy directories |
09ed3099 | 473 | recursively. See also --dirs (-d). |
41059f75 AT |
474 | |
475 | dit(bf(-R, --relative)) Use relative paths. This means that the full path | |
476 | names specified on the command line are sent to the server rather than | |
477 | just the last parts of the filenames. This is particularly useful when | |
14d43f1f DD |
478 | you want to send several different directories at the same time. For |
479 | example, if you used the command | |
41059f75 | 480 | |
9bef934c | 481 | verb(rsync /foo/bar/foo.c remote:/tmp/) |
41059f75 AT |
482 | |
483 | then this would create a file called foo.c in /tmp/ on the remote | |
484 | machine. If instead you used | |
485 | ||
9bef934c | 486 | verb(rsync -R /foo/bar/foo.c remote:/tmp/) |
41059f75 AT |
487 | |
488 | then a file called /tmp/foo/bar/foo.c would be created on the remote | |
9bef934c WD |
489 | machine -- the full path name is preserved. To limit the amount of |
490 | path information that is sent, do something like this: | |
491 | ||
492 | verb(cd /foo | |
493 | rsync -R bar/foo.c remote:/tmp/) | |
494 | ||
495 | That would create /tmp/bar/foo.c on the remote machine. | |
f177b7cc WD |
496 | |
497 | dit(bf(--no-relative)) Turn off the --relative option. This is only | |
498 | needed if you want to use --files-from without its implied --relative | |
499 | file processing. | |
500 | ||
501 | dit(bf(--no-implied-dirs)) When combined with the --relative option, the | |
502 | implied directories in each path are not explicitly duplicated as part | |
503 | of the transfer. This makes the transfer more optimal and also allows | |
504 | the two sides to have non-matching symlinks in the implied part of the | |
505 | path. For instance, if you transfer the file "/path/foo/file" with -R, | |
506 | the default is for rsync to ensure that "/path" and "/path/foo" on the | |
507 | destination exactly match the directories/symlinks of the source. Using | |
508 | the --no-implied-dirs option would omit both of these implied dirs, | |
509 | which means that if "/path" was a real directory on one machine and a | |
510 | symlink of the other machine, rsync would not try to change this. | |
41059f75 | 511 | |
b19fd07c WD |
512 | dit(bf(-b, --backup)) With this option, preexisting destination files are |
513 | renamed as each file is transferred or deleted. You can control where the | |
514 | backup file goes and what (if any) suffix gets appended using the | |
515 | --backup-dir and --suffix options. | |
41059f75 | 516 | |
66203a98 AT |
517 | dit(bf(--backup-dir=DIR)) In combination with the --backup option, this |
518 | tells rsync to store all backups in the specified directory. This is | |
759ac870 DD |
519 | very useful for incremental backups. You can additionally |
520 | specify a backup suffix using the --suffix option | |
521 | (otherwise the files backed up in the specified directory | |
522 | will keep their original filenames). | |
0b79c324 WD |
523 | If DIR is a relative path, it is relative to the destination directory |
524 | (which changes in a recursive transfer). | |
66203a98 | 525 | |
b5679335 | 526 | dit(bf(--suffix=SUFFIX)) This option allows you to override the default |
b19fd07c WD |
527 | backup suffix used with the --backup (-b) option. The default suffix is a ~ |
528 | if no --backup-dir was specified, otherwise it is an empty string. | |
9ef53907 | 529 | |
4539c0d7 WD |
530 | dit(bf(-u, --update)) This forces rsync to skip any files which exist on |
531 | the destination and have a modified time that is newer than the source | |
532 | file. (If an existing destination file has a modify time equal to the | |
533 | source file's, it will be updated if the sizes are different.) | |
41059f75 | 534 | |
4539c0d7 WD |
535 | In the current implementation of --update, a difference of file format |
536 | between the sender and receiver is always | |
adddd075 WD |
537 | considered to be important enough for an update, no matter what date |
538 | is on the objects. In other words, if the source has a directory or a | |
539 | symlink where the destination has a file, the transfer would occur | |
540 | regardless of the timestamps. This might change in the future (feel | |
541 | free to comment on this on the mailing list if you have an opinion). | |
542 | ||
a3221d2a WD |
543 | dit(bf(--inplace)) This causes rsync not to create a new copy of the file |
544 | and then move it into place. Instead rsync will overwrite the existing | |
eb162f3b WD |
545 | file, meaning that the rsync algorithm can't accomplish the full amount of |
546 | network reduction it might be able to otherwise (since it does not yet try | |
547 | to sort data matches). One exception to this is if you combine the option | |
548 | with --backup, since rsync is smart enough to use the backup file as the | |
549 | basis file for the transfer. | |
a3221d2a | 550 | |
183150b7 WD |
551 | This option is useful for transfer of large files with block-based changes |
552 | or appended data, and also on systems that are disk bound, not network | |
553 | bound. | |
554 | ||
555 | The option implies --partial (since an interrupted transfer does not delete | |
01b835c2 WD |
556 | the file), but conflicts with --partial-dir and --delay-updates. |
557 | Prior to rsync 2.6.4 --inplace was also incompatible with --compare-dest, | |
558 | --copy-dest, and --link-dest. | |
a3221d2a | 559 | |
399371e7 | 560 | WARNING: The file's data will be in an inconsistent state during the |
98f51bfb | 561 | transfer (and possibly afterward if the transfer gets interrupted), so you |
399371e7 | 562 | should not use this option to update files that are in use. Also note that |
eb162f3b | 563 | rsync will be unable to update a file in-place that is not writable by the |
75b243a5 | 564 | receiving user. |
a3221d2a | 565 | |
09ed3099 WD |
566 | dit(bf(-d, --dirs)) Tell the sending side to include any directories that |
567 | are encountered. Unlike --recursive, a directory's contents are not copied | |
568 | unless the directory was specified on the command-line as either "." or a | |
569 | name with a trailing slash (e.g. "foo/"). Without this option or the | |
570 | --recursive option, rsync will skip all directories it encounters (and | |
571 | output a message to that effect for each one). | |
572 | ||
eb06fa95 MP |
573 | dit(bf(-l, --links)) When symlinks are encountered, recreate the |
574 | symlink on the destination. | |
41059f75 | 575 | |
eb06fa95 | 576 | dit(bf(-L, --copy-links)) When symlinks are encountered, the file that |
ef855d19 WD |
577 | they point to (the referent) is copied, rather than the symlink. In older |
578 | versions of rsync, this option also had the side-effect of telling the | |
579 | receiving side to follow symlinks, such as symlinks to directories. In a | |
580 | modern rsync such as this one, you'll need to specify --keep-dirlinks (-K) | |
581 | to get this extra behavior. The only exception is when sending files to | |
582 | an rsync that is too old to understand -K -- in that case, the -L option | |
583 | will still have the side-effect of -K on that older receiving rsync. | |
b5313607 | 584 | |
eb06fa95 | 585 | dit(bf(--copy-unsafe-links)) This tells rsync to copy the referent of |
7af4227a | 586 | symbolic links that point outside the copied tree. Absolute symlinks |
eb06fa95 MP |
587 | are also treated like ordinary files, and so are any symlinks in the |
588 | source path itself when --relative is used. | |
41059f75 | 589 | |
d310a212 | 590 | dit(bf(--safe-links)) This tells rsync to ignore any symbolic links |
7af4227a | 591 | which point outside the copied tree. All absolute symlinks are |
d310a212 | 592 | also ignored. Using this option in conjunction with --relative may |
14d43f1f | 593 | give unexpected results. |
d310a212 | 594 | |
41059f75 AT |
595 | dit(bf(-H, --hard-links)) This tells rsync to recreate hard links on |
596 | the remote system to be the same as the local system. Without this | |
597 | option hard links are treated like regular files. | |
598 | ||
599 | Note that rsync can only detect hard links if both parts of the link | |
600 | are in the list of files being sent. | |
601 | ||
602 | This option can be quite slow, so only use it if you need it. | |
603 | ||
09ed3099 WD |
604 | dit(bf(-K, --keep-dirlinks)) On the receiving side, if a symlink is |
605 | pointing to a directory, it will be treated as matching a directory | |
606 | from the sender. | |
607 | ||
41059f75 | 608 | dit(bf(-W, --whole-file)) With this option the incremental rsync algorithm |
a1a440c2 DD |
609 | is not used and the whole file is sent as-is instead. The transfer may be |
610 | faster if this option is used when the bandwidth between the source and | |
6eb770bb | 611 | destination machines is higher than the bandwidth to disk (especially when the |
4d888108 | 612 | "disk" is actually a networked filesystem). This is the default when both |
6eb770bb | 613 | the source and destination are specified as local paths. |
41059f75 | 614 | |
93689aa5 DD |
615 | dit(bf(--no-whole-file)) Turn off --whole-file, for use when it is the |
616 | default. | |
617 | ||
8dc74608 WD |
618 | dit(bf(-p, --perms)) This option causes rsync to set the destination |
619 | permissions to be the same as the source permissions. | |
620 | ||
621 | Without this option, each new file gets its permissions set based on the | |
622 | source file's permissions and the umask at the receiving end, while all | |
623 | other files (including updated files) retain their existing permissions | |
624 | (which is the same behavior as other file-copy utilities, such as cp). | |
41059f75 | 625 | |
eb06fa95 MP |
626 | dit(bf(-o, --owner)) This option causes rsync to set the owner of the |
627 | destination file to be the same as the source file. On most systems, | |
a2b0471f WD |
628 | only the super-user can set file ownership. By default, the preservation |
629 | is done by name, but may fall back to using the ID number in some | |
630 | circumstances. See the --numeric-ids option for a full discussion. | |
41059f75 | 631 | |
eb06fa95 MP |
632 | dit(bf(-g, --group)) This option causes rsync to set the group of the |
633 | destination file to be the same as the source file. If the receiving | |
634 | program is not running as the super-user, only groups that the | |
a2b0471f WD |
635 | receiver is a member of will be preserved. By default, the preservation |
636 | is done by name, but may fall back to using the ID number in some | |
637 | circumstances. See the --numeric-ids option for a full discussion. | |
41059f75 AT |
638 | |
639 | dit(bf(-D, --devices)) This option causes rsync to transfer character and | |
640 | block device information to the remote system to recreate these | |
641 | devices. This option is only available to the super-user. | |
642 | ||
643 | dit(bf(-t, --times)) This tells rsync to transfer modification times along | |
baf3e504 DD |
644 | with the files and update them on the remote system. Note that if this |
645 | option is not used, the optimization that excludes files that have not been | |
646 | modified cannot be effective; in other words, a missing -t or -a will | |
d0bc3520 WD |
647 | cause the next transfer to behave as if it used -I, causing all files to be |
648 | updated (though the rsync algorithm will make the update fairly efficient | |
649 | if the files haven't actually changed, you're much better off using -t). | |
41059f75 | 650 | |
54e66f1d | 651 | dit(bf(-O, --omit-dir-times)) This tells rsync to omit directories when |
f5a7b9e7 WD |
652 | it is preserving modification times (see --times). If NFS is sharing |
653 | the directories on the receiving side, it is a good idea to use -O. | |
54e66f1d | 654 | |
41059f75 AT |
655 | dit(bf(-n, --dry-run)) This tells rsync to not do any file transfers, |
656 | instead it will just report the actions it would have taken. | |
657 | ||
658 | dit(bf(-S, --sparse)) Try to handle sparse files efficiently so they take | |
659 | up less space on the destination. | |
660 | ||
d310a212 AT |
661 | NOTE: Don't use this option when the destination is a Solaris "tmpfs" |
662 | filesystem. It doesn't seem to handle seeks over null regions | |
663 | correctly and ends up corrupting the files. | |
664 | ||
41059f75 AT |
665 | dit(bf(-x, --one-file-system)) This tells rsync not to cross filesystem |
666 | boundaries when recursing. This is useful for transferring the | |
667 | contents of only one filesystem. | |
668 | ||
1347d512 AT |
669 | dit(bf(--existing)) This tells rsync not to create any new files - |
670 | only update files that already exist on the destination. | |
671 | ||
3d6feada MP |
672 | dit(bf(--ignore-existing)) |
673 | This tells rsync not to update files that already exist on | |
674 | the destination. | |
675 | ||
0b73ca12 AT |
676 | dit(bf(--max-delete=NUM)) This tells rsync not to delete more than NUM |
677 | files or directories. This is useful when mirroring very large trees | |
678 | to prevent disasters. | |
679 | ||
3610c458 WD |
680 | dit(bf(--max-size=SIZE)) This tells rsync to avoid transferring any |
681 | file that is larger than the specified SIZE. The SIZE value can be | |
682 | suffixed with a letter to indicate a size multiplier (K, M, or G) and | |
683 | may be a fractional value (e.g. "--max-size=1.5m"). | |
684 | ||
2c0fa6c5 | 685 | dit(bf(--delete)) This tells rsync to delete extraneous files from the |
e8b155a3 WD |
686 | receiving side (ones that aren't on the sending side), but only for the |
687 | directories that are being synchronized. You must have asked rsync to | |
688 | send the whole directory (e.g. "dir" or "dir/") without using a wildcard | |
689 | for the directory's contents (e.g. "dir/*") since the wildcard is expanded | |
ae76a740 | 690 | by the shell and rsync thus gets a request to transfer individual files, not |
e8b155a3 WD |
691 | the files' parent directory. Files that are excluded from transfer are |
692 | excluded from being deleted unless you use --delete-excluded. | |
41059f75 | 693 | |
866925bf | 694 | This option has no effect unless directory recursion is enabled. |
24986abd | 695 | |
b33b791e | 696 | This option can be dangerous if used incorrectly! It is a very good idea |
e8b155a3 | 697 | to run first using the --dry-run option (-n) to see what files would be |
b33b791e | 698 | deleted to make sure important files aren't listed. |
41059f75 | 699 | |
e8b155a3 | 700 | If the sending side detects any I/O errors, then the deletion of any |
3e578a19 AT |
701 | files at the destination will be automatically disabled. This is to |
702 | prevent temporary filesystem failures (such as NFS errors) on the | |
703 | sending side causing a massive deletion of files on the | |
2c5548d2 | 704 | destination. You can override this with the --ignore-errors option. |
41059f75 | 705 | |
2c0fa6c5 WD |
706 | The --delete option may be combined with one of the --delete-WHEN options |
707 | without conflict, as well as --delete-excluded. However, if none of the | |
708 | --delete-WHEN options are specified, rsync will currently choose the | |
709 | --delete-before algorithm. A future version may change this to choose the | |
710 | --delete-during algorithm. See also --delete-after. | |
711 | ||
712 | dit(bf(--delete-before)) Request that the file-deletions on the receiving | |
713 | side be done before the transfer starts. This is the default if --delete | |
714 | or --delete-excluded is specified without one of the --delete-WHEN options. | |
715 | See --delete (which is implied) for more details on file-deletion. | |
716 | ||
717 | Deleting before the transfer is helpful if the filesystem is tight for space | |
aaca3daa | 718 | and removing extraneous files would help to make the transfer possible. |
ae76a740 WD |
719 | However, it does introduce a delay before the start of the transfer, |
720 | and this delay might cause the transfer to timeout (if --timeout was | |
721 | specified). | |
722 | ||
2c0fa6c5 WD |
723 | dit(bf(--delete-during, --del)) Request that the file-deletions on the |
724 | receiving side be done incrementally as the transfer happens. This is | |
725 | a faster method than chosing the before- or after-transfer algorithm, | |
ae76a740 WD |
726 | but it is only supported beginning with rsync version 2.6.4. |
727 | See --delete (which is implied) for more details on file-deletion. | |
aaca3daa | 728 | |
2c0fa6c5 | 729 | dit(bf(--delete-after)) Request that the file-deletions on the receiving |
ae76a740 WD |
730 | side be done after the transfer has completed. This is useful if you |
731 | are sending new per-directory merge files as a part of the transfer and | |
732 | you want their exclusions to take effect for the delete phase of the | |
733 | current transfer. | |
734 | See --delete (which is implied) for more details on file-deletion. | |
e8b155a3 | 735 | |
866925bf WD |
736 | dit(bf(--delete-excluded)) In addition to deleting the files on the |
737 | receiving side that are not on the sending side, this tells rsync to also | |
738 | delete any files on the receiving side that are excluded (see --exclude). | |
ae76a740 | 739 | See --delete (which is implied) for more details on file-deletion. |
866925bf | 740 | |
2c5548d2 | 741 | dit(bf(--ignore-errors)) Tells --delete to go ahead and delete files |
b5accaba | 742 | even when there are I/O errors. |
2c5548d2 | 743 | |
b695d088 DD |
744 | dit(bf(--force)) This options tells rsync to delete directories even if |
745 | they are not empty when they are to be replaced by non-directories. This | |
746 | is only relevant without --delete because deletions are now done depth-first. | |
747 | Requires the --recursive option (which is implied by -a) to have any effect. | |
41059f75 | 748 | |
3ed8eb3f WD |
749 | dit(bf(-B, --block-size=BLOCKSIZE)) This forces the block size used in |
750 | the rsync algorithm to a fixed value. It is normally selected based on | |
751 | the size of each file being updated. See the technical report for details. | |
41059f75 | 752 | |
b5679335 | 753 | dit(bf(-e, --rsh=COMMAND)) This option allows you to choose an alternative |
41059f75 | 754 | remote shell program to use for communication between the local and |
43cd760f WD |
755 | remote copies of rsync. Typically, rsync is configured to use ssh by |
756 | default, but you may prefer to use rsh on a local network. | |
41059f75 | 757 | |
bef49340 | 758 | If this option is used with bf([user@]host::module/path), then the |
4d888108 | 759 | remote shell em(COMMAND) will be used to run an rsync server on the |
bef49340 WD |
760 | remote host, and all data will be transmitted through that remote |
761 | shell connection, rather than through a direct socket connection to a | |
2d4ca358 DD |
762 | running rsync server on the remote host. See the section "CONNECTING |
763 | TO AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM" above. | |
bef49340 | 764 | |
ea7f8108 WD |
765 | Command-line arguments are permitted in COMMAND provided that COMMAND is |
766 | presented to rsync as a single argument. For example: | |
98393ae2 | 767 | |
ea7f8108 | 768 | quote(-e "ssh -p 2234") |
98393ae2 WD |
769 | |
770 | (Note that ssh users can alternately customize site-specific connect | |
771 | options in their .ssh/config file.) | |
772 | ||
41059f75 | 773 | You can also choose the remote shell program using the RSYNC_RSH |
ea7f8108 | 774 | environment variable, which accepts the same range of values as -e. |
41059f75 | 775 | |
735a816e DD |
776 | See also the --blocking-io option which is affected by this option. |
777 | ||
b5679335 | 778 | dit(bf(--rsync-path=PATH)) Use this to specify the path to the copy of |
d73ee7b7 AT |
779 | rsync on the remote machine. Useful when it's not in your path. Note |
780 | that this is the full path to the binary, not just the directory that | |
781 | the binary is in. | |
41059f75 | 782 | |
f177b7cc WD |
783 | dit(bf(-C, --cvs-exclude)) This is a useful shorthand for excluding a |
784 | broad range of files that you often don't want to transfer between | |
785 | systems. It uses the same algorithm that CVS uses to determine if | |
786 | a file should be ignored. | |
787 | ||
788 | The exclude list is initialized to: | |
789 | ||
2a383be0 WD |
790 | quote(RCS SCCS CVS CVS.adm RCSLOG cvslog.* tags TAGS .make.state |
791 | .nse_depinfo *~ #* .#* ,* _$* *$ *.old *.bak *.BAK *.orig *.rej | |
792 | .del-* *.a *.olb *.o *.obj *.so *.exe *.Z *.elc *.ln core .svn/) | |
f177b7cc WD |
793 | |
794 | then files listed in a $HOME/.cvsignore are added to the list and any | |
2a383be0 WD |
795 | files listed in the CVSIGNORE environment variable (all cvsignore names |
796 | are delimited by whitespace). | |
797 | ||
f177b7cc | 798 | Finally, any file is ignored if it is in the same directory as a |
2a383be0 | 799 | .cvsignore file and matches one of the patterns listed therein. |
2a383be0 | 800 | See the bf(cvs(1)) manual for more information. |
f177b7cc | 801 | |
16e5de84 WD |
802 | dit(bf(-f, --filter=RULE)) This option allows you to add rules to selectively |
803 | exclude certain files from the list of files to be transferred. This is | |
804 | most useful in combination with a recursive transfer. | |
41059f75 | 805 | |
16e5de84 | 806 | You may use as many --filter options on the command line as you like |
41059f75 AT |
807 | to build up the list of files to exclude. |
808 | ||
16e5de84 WD |
809 | See the FILTER RULES section for detailed information on this option. |
810 | ||
811 | dit(bf(-F)) The -F option is a shorthand for adding two --filter rules to | |
812 | your command. The first time it is used is a shorthand for this rule: | |
813 | ||
814 | verb( | |
815 | --filter=': /.rsync-filter' | |
816 | ) | |
817 | ||
818 | This tells rsync to look for per-directory .rsync-filter files that have | |
819 | been sprinkled through the hierarchy and use their rules to filter the | |
820 | files in the transfer. If -F is repeated, it is a shorthand for this | |
821 | rule: | |
822 | ||
823 | verb( | |
824 | --filter='- .rsync-filter' | |
825 | ) | |
826 | ||
827 | This filters out the .rsync-filter files themselves from the transfer. | |
828 | ||
829 | See the FILTER RULES section for detailed information on how these options | |
830 | work. | |
831 | ||
832 | dit(bf(--exclude=PATTERN)) This option is a simplified form of the | |
833 | --filter option that defaults to an exclude rule and does not allow | |
834 | the full rule-parsing syntax of normal filter rules. | |
835 | ||
836 | See the FILTER RULES section for detailed information on this option. | |
41059f75 | 837 | |
b5679335 | 838 | dit(bf(--exclude-from=FILE)) This option is similar to the --exclude |
c48b22c8 AT |
839 | option, but instead it adds all exclude patterns listed in the file |
840 | FILE to the exclude list. Blank lines in FILE and lines starting with | |
841 | ';' or '#' are ignored. | |
f8a94f0d DD |
842 | If em(FILE) is bf(-) the list will be read from standard input. |
843 | ||
16e5de84 WD |
844 | dit(bf(--include=PATTERN)) This option is a simplified form of the |
845 | --filter option that defaults to an include rule and does not allow | |
846 | the full rule-parsing syntax of normal filter rules. | |
43bd68e5 | 847 | |
16e5de84 | 848 | See the FILTER RULES section for detailed information on this option. |
43bd68e5 | 849 | |
b5679335 | 850 | dit(bf(--include-from=FILE)) This specifies a list of include patterns |
43bd68e5 | 851 | from a file. |
c769702f | 852 | If em(FILE) is "-" the list will be read from standard input. |
f8a94f0d | 853 | |
f177b7cc WD |
854 | dit(bf(--files-from=FILE)) Using this option allows you to specify the |
855 | exact list of files to transfer (as read from the specified FILE or "-" | |
c769702f | 856 | for standard input). It also tweaks the default behavior of rsync to make |
f177b7cc WD |
857 | transferring just the specified files and directories easier. For |
858 | instance, the --relative option is enabled by default when this option | |
859 | is used (use --no-relative if you want to turn that off), all | |
860 | directories specified in the list are created on the destination (rather | |
861 | than being noisily skipped without -r), and the -a (--archive) option's | |
862 | behavior does not imply -r (--recursive) -- specify it explicitly, if | |
863 | you want it. | |
864 | ||
865 | The file names that are read from the FILE are all relative to the | |
866 | source dir -- any leading slashes are removed and no ".." references are | |
867 | allowed to go higher than the source dir. For example, take this | |
868 | command: | |
869 | ||
870 | quote(rsync -a --files-from=/tmp/foo /usr remote:/backup) | |
871 | ||
872 | If /tmp/foo contains the string "bin" (or even "/bin"), the /usr/bin | |
873 | directory will be created as /backup/bin on the remote host (but the | |
874 | contents of the /usr/bin dir would not be sent unless you specified -r | |
875 | or the names were explicitly listed in /tmp/foo). Also keep in mind | |
876 | that the effect of the (enabled by default) --relative option is to | |
877 | duplicate only the path info that is read from the file -- it does not | |
878 | force the duplication of the source-spec path (/usr in this case). | |
879 | ||
880 | In addition, the --files-from file can be read from the remote host | |
881 | instead of the local host if you specify a "host:" in front of the file | |
882 | (the host must match one end of the transfer). As a short-cut, you can | |
883 | specify just a prefix of ":" to mean "use the remote end of the | |
884 | transfer". For example: | |
885 | ||
886 | quote(rsync -a --files-from=:/path/file-list src:/ /tmp/copy) | |
887 | ||
888 | This would copy all the files specified in the /path/file-list file that | |
889 | was located on the remote "src" host. | |
890 | ||
891 | dit(bf(-0, --from0)) This tells rsync that the filenames it reads from a | |
892 | file are terminated by a null ('\0') character, not a NL, CR, or CR+LF. | |
16e5de84 WD |
893 | This affects --exclude-from, --include-from, --files-from, and any |
894 | merged files specified in a --filter rule. | |
f01b6368 WD |
895 | It does not affect --cvs-exclude (since all names read from a .cvsignore |
896 | file are split on whitespace). | |
41059f75 | 897 | |
b5679335 | 898 | dit(bf(-T, --temp-dir=DIR)) This option instructs rsync to use DIR as a |
375a4556 | 899 | scratch directory when creating temporary copies of the files |
41059f75 AT |
900 | transferred on the receiving side. The default behavior is to create |
901 | the temporary files in the receiving directory. | |
902 | ||
b127c1dc | 903 | dit(bf(--compare-dest=DIR)) This option instructs rsync to use em(DIR) on |
e49f61f5 WD |
904 | the destination machine as an additional hierarchy to compare destination |
905 | files against doing transfers (if the files are missing in the destination | |
906 | directory). If a file is found in em(DIR) that is identical to the | |
907 | sender's file, the file will NOT be transferred to the destination | |
908 | directory. This is useful for creating a sparse backup of just files that | |
909 | have changed from an earlier backup. | |
910 | ||
911 | Beginning in version 2.6.4, multiple --compare-dest directories may be | |
912 | provided and rsync will search the list in the order specified until it | |
913 | finds an existing file. That first discovery is used as the basis file, | |
914 | and also determines if the transfer needs to happen. | |
915 | ||
916 | If em(DIR) is a relative path, it is relative to the destination directory. | |
917 | See also --copy-dest and --link-dest. | |
b127c1dc WD |
918 | |
919 | dit(bf(--copy-dest=DIR)) This option behaves like bf(--compare-dest), but | |
920 | rsync will also copy unchanged files found in em(DIR) to the destination | |
921 | directory (using the data in the em(DIR) for an efficient copy). This is | |
922 | useful for doing transfers to a new destination while leaving existing | |
923 | files intact, and then doing a flash-cutover when all files have been | |
e49f61f5 WD |
924 | successfully transferred. |
925 | ||
926 | If em(DIR) is a relative path, it is relative to the destination directory. | |
927 | See also --compare-dest and --link-dest. | |
b127c1dc WD |
928 | |
929 | dit(bf(--link-dest=DIR)) This option behaves like bf(--copy-dest), but | |
e49f61f5 WD |
930 | unchanged files are hard linked from em(DIR) to the destination directory. |
931 | The files must be identical in all preserved attributes (e.g. permissions, | |
932 | possibly ownership) in order for the files to be linked together. | |
8429aa9e WD |
933 | An example: |
934 | ||
935 | verb( | |
936 | rsync -av --link-dest=$PWD/prior_dir host:src_dir/ new_dir/ | |
937 | ) | |
59c95e42 | 938 | |
e49f61f5 WD |
939 | Beginning with version 2.6.4, if more than one --link-dest option is |
940 | specified, rsync will try to find an exact match to link with (searching | |
941 | the list in the order specified), and if not found, a basis file from one | |
942 | of the em(DIR)s will be selected to try to speed up the transfer. | |
943 | ||
944 | If em(DIR) is a relative path, it is relative to the destination directory. | |
945 | See also --compare-dest and --copy-dest. | |
b127c1dc | 946 | |
e0204f56 WD |
947 | Note that rsync versions prior to 2.6.1 had a bug that could prevent |
948 | --link-dest from working properly for a non-root user when -o was specified | |
eb162f3b WD |
949 | (or implied by -a). You can work-around this bug by avoiding the -o option |
950 | when sending to an old rsync. | |
e0204f56 | 951 | |
41059f75 | 952 | dit(bf(-z, --compress)) With this option, rsync compresses any data from |
089e73f8 | 953 | the files that it sends to the destination machine. This |
f39281ae | 954 | option is useful on slow connections. The compression method used is the |
41059f75 AT |
955 | same method that gzip uses. |
956 | ||
957 | Note this this option typically achieves better compression ratios | |
958 | that can be achieved by using a compressing remote shell, or a | |
959 | compressing transport, as it takes advantage of the implicit | |
960 | information sent for matching data blocks. | |
961 | ||
962 | dit(bf(--numeric-ids)) With this option rsync will transfer numeric group | |
4d888108 | 963 | and user IDs rather than using user and group names and mapping them |
41059f75 AT |
964 | at both ends. |
965 | ||
4d888108 | 966 | By default rsync will use the username and groupname to determine |
41059f75 | 967 | what ownership to give files. The special uid 0 and the special group |
14d43f1f | 968 | 0 are never mapped via user/group names even if the --numeric-ids |
41059f75 AT |
969 | option is not specified. |
970 | ||
ec40899b WD |
971 | If a user or group has no name on the source system or it has no match |
972 | on the destination system, then the numeric ID | |
973 | from the source system is used instead. See also the comments on the | |
a2b0471f WD |
974 | "use chroot" setting in the rsyncd.conf manpage for information on how |
975 | the chroot setting affects rsync's ability to look up the names of the | |
976 | users and groups and what you can do about it. | |
41059f75 | 977 | |
b5accaba | 978 | dit(bf(--timeout=TIMEOUT)) This option allows you to set a maximum I/O |
de2fd20e AT |
979 | timeout in seconds. If no data is transferred for the specified time |
980 | then rsync will exit. The default is 0, which means no timeout. | |
41059f75 | 981 | |
c259892c WD |
982 | dit(bf(--port=PORT)) This specifies an alternate TCP port number to use |
983 | rather than the default of 873. This is only needed if you are using the | |
984 | double-colon (::) syntax to connect with an rsync daemon (since the URL | |
985 | syntax has a way to specify the port as a part of the URL). See also this | |
986 | option in the --daemon mode section. | |
987 | ||
b5accaba | 988 | dit(bf(--blocking-io)) This tells rsync to use blocking I/O when launching |
314a74d7 WD |
989 | a remote shell transport. If the remote shell is either rsh or remsh, |
990 | rsync defaults to using | |
b5accaba WD |
991 | blocking I/O, otherwise it defaults to using non-blocking I/O. (Note that |
992 | ssh prefers non-blocking I/O.) | |
64c704f0 | 993 | |
93689aa5 DD |
994 | dit(bf(--no-blocking-io)) Turn off --blocking-io, for use when it is the |
995 | default. | |
996 | ||
3a64ad1f | 997 | dit(bf(--log-format=FORMAT)) This allows you to specify exactly what the |
14d43f1f | 998 | rsync client logs to stdout on a per-file basis. The log format is |
3a64ad1f DD |
999 | specified using the same format conventions as the log format option in |
1000 | rsyncd.conf. | |
b6062654 | 1001 | |
b72f24c7 AT |
1002 | dit(bf(--stats)) This tells rsync to print a verbose set of statistics |
1003 | on the file transfer, allowing you to tell how effective the rsync | |
e19452a9 | 1004 | algorithm is for your data. |
b72f24c7 | 1005 | |
d9fcc198 AT |
1006 | dit(bf(--partial)) By default, rsync will delete any partially |
1007 | transferred file if the transfer is interrupted. In some circumstances | |
1008 | it is more desirable to keep partially transferred files. Using the | |
1009 | --partial option tells rsync to keep the partial file which should | |
1010 | make a subsequent transfer of the rest of the file much faster. | |
1011 | ||
44cad59f | 1012 | dit(bf(--partial-dir=DIR)) Turns on --partial mode, but tells rsync to |
b127c1dc | 1013 | put a partially transferred file into em(DIR) instead of writing out the |
44cad59f WD |
1014 | file to the destination dir. Rsync will also use a file found in this |
1015 | dir as data to speed up the transfer (i.e. when you redo the send after | |
1016 | rsync creates a partial file) and delete such a file after it has served | |
b90a6d9f WD |
1017 | its purpose. Note that if --whole-file is specified (or implied) that an |
1018 | existing partial-dir file will not be used to speedup the transfer (since | |
1019 | rsync is sending files without using the incremental rsync algorithm). | |
44cad59f WD |
1020 | |
1021 | Rsync will create the dir if it is missing (just the last dir -- not the | |
1022 | whole path). This makes it easy to use a relative path (such as | |
1023 | "--partial-dir=.rsync-partial") to have rsync create the partial-directory | |
b127c1dc | 1024 | in the destination file's directory (rsync will also try to remove the em(DIR) |
44cad59f WD |
1025 | if a partial file was found to exist at the start of the transfer and the |
1026 | DIR was specified as a relative path). | |
1027 | ||
a33857da WD |
1028 | If the partial-dir value is not an absolute path, rsync will also add an |
1029 | --exclude of this value at the end of all your existing excludes. This | |
1030 | will prevent partial-dir files from being transferred and also prevent the | |
1031 | untimely deletion of partial-dir items on the receiving side. An example: | |
1032 | the above --partial-dir option would add an "--exclude=.rsync-partial/" | |
16e5de84 WD |
1033 | rule at the end of any other filter rules. Note that if you are |
1034 | supplying your own filter rules, you may need to manually insert a | |
a33857da WD |
1035 | rule for this directory exclusion somewhere higher up in the list so that |
1036 | it has a high enough priority to be effective (e.g., if your rules specify | |
1037 | a trailing --exclude=* rule, the auto-added rule will be ineffective). | |
44cad59f | 1038 | |
b4d1e854 WD |
1039 | IMPORTANT: the --partial-dir should not be writable by other users or it |
1040 | is a security risk. E.g. AVOID "/tmp". | |
1041 | ||
1042 | You can also set the partial-dir value the RSYNC_PARTIAL_DIR environment | |
1043 | variable. Setting this in the environment does not force --partial to be | |
01b835c2 WD |
1044 | enabled, but rather it effects where partial files go when --partial is |
1045 | specified. For instance, instead of using --partial-dir=.rsync-tmp | |
b4d1e854 WD |
1046 | along with --progress, you could set RSYNC_PARTIAL_DIR=.rsync-tmp in your |
1047 | environment and then just use the -P option to turn on the use of the | |
01b835c2 WD |
1048 | .rsync-tmp dir for partial transfers. The only time that the --partial |
1049 | option does not look for this environment value is (1) when --inplace was | |
1050 | specified (since --inplace conflicts with --partial-dir), or (2) when | |
1051 | --delay-updates was specified (see below). | |
1052 | ||
1053 | dit(bf(--delay-updates)) This option puts the temporary file from each | |
1054 | updated file into the file's partial-dir (see above) until the end of the | |
1055 | transfer, at which time all the files are renamed into place in rapid | |
1056 | succession. This attempts to make the updating of the files a little more | |
1057 | atomic. If you don't specify the --partial-dir option, this option will | |
1058 | cause it to default to ".~tmp~" (RSYNC_PARTIAL_DIR is not consulted for | |
1059 | this value). Conflicts with --inplace. | |
1060 | ||
1061 | This option uses more memory on the receiving side (one bit per file | |
1062 | transferred) and also requires enough free disk space on the receiving | |
1063 | side to hold an additional copy of all the updated files. Note also that | |
1064 | you should not use an absolute path to --partial-dir unless there is no | |
1065 | chance of any of the files in the transfer having the same name (since all | |
1066 | the updated files will be put into a single directory if the path is | |
1067 | absolute). | |
1068 | ||
1069 | See also the "atomic-rsync" perl script in the "support" subdir for an | |
1070 | update algorithm that is even more atomic (it uses --link-dest and a | |
1071 | parallel hierarchy of files). | |
44cad59f | 1072 | |
eb86d661 AT |
1073 | dit(bf(--progress)) This option tells rsync to print information |
1074 | showing the progress of the transfer. This gives a bored user | |
1075 | something to watch. | |
e2559dbe | 1076 | Implies --verbose without incrementing verbosity. |
7b10f91d | 1077 | |
68f9910d WD |
1078 | When the file is transferring, the data looks like this: |
1079 | ||
1080 | verb( | |
1081 | 782448 63% 110.64kB/s 0:00:04 | |
1082 | ) | |
1083 | ||
1084 | This tells you the current file size, the percentage of the transfer that | |
1085 | is complete, the current calculated file-completion rate (including both | |
1086 | data over the wire and data being matched locally), and the estimated time | |
1087 | remaining in this transfer. | |
1088 | ||
c2c14fa2 | 1089 | After a file is complete, the data looks like this: |
68f9910d WD |
1090 | |
1091 | verb( | |
1092 | 1238099 100% 146.38kB/s 0:00:08 (5, 57.1% of 396) | |
1093 | ) | |
1094 | ||
1095 | This tells you the final file size, that it's 100% complete, the final | |
1096 | transfer rate for the file, the amount of elapsed time it took to transfer | |
1097 | the file, and the addition of a total-transfer summary in parentheses. | |
1098 | These additional numbers tell you how many files have been updated, and | |
1099 | what percent of the total number of files has been scanned. | |
1100 | ||
183150b7 WD |
1101 | dit(bf(-P)) The -P option is equivalent to --partial --progress. Its |
1102 | purpose is to make it much easier to specify these two options for a long | |
1103 | transfer that may be interrupted. | |
d9fcc198 | 1104 | |
65575e96 AT |
1105 | dit(bf(--password-file)) This option allows you to provide a password |
1106 | in a file for accessing a remote rsync server. Note that this option | |
bb18e755 | 1107 | is only useful when accessing an rsync server using the built in |
65575e96 | 1108 | transport, not when using a remote shell as the transport. The file |
fc7952e7 AT |
1109 | must not be world readable. It should contain just the password as a |
1110 | single line. | |
65575e96 | 1111 | |
09ed3099 WD |
1112 | dit(bf(--list-only)) This option will cause the source files to be listed |
1113 | instead of transferred. This option is inferred if there is no destination | |
1114 | specified, so you don't usually need to use it explicitly. However, it can | |
1115 | come in handy for a power user that wants to avoid the "-r --exclude="/*/*" | |
1116 | options that rsync might use as a compatibility kluge when generating a | |
1117 | non-recursive listing. | |
1118 | ||
ef5d23eb DD |
1119 | dit(bf(--bwlimit=KBPS)) This option allows you to specify a maximum |
1120 | transfer rate in kilobytes per second. This option is most effective when | |
1121 | using rsync with large files (several megabytes and up). Due to the nature | |
1122 | of rsync transfers, blocks of data are sent, then if rsync determines the | |
1123 | transfer was too fast, it will wait before sending the next data block. The | |
4d888108 | 1124 | result is an average transfer rate equaling the specified limit. A value |
ef5d23eb DD |
1125 | of zero specifies no limit. |
1126 | ||
b9f592fb | 1127 | dit(bf(--write-batch=FILE)) Record a file that can later be applied to |
98f51bfb | 1128 | another identical destination with --read-batch. See the "BATCH MODE" |
b9f592fb | 1129 | section for details. |
6902ed17 | 1130 | |
b9f592fb | 1131 | dit(bf(--read-batch=FILE)) Apply all of the changes stored in FILE, a |
c769702f | 1132 | file previously generated by --write-batch. |
399371e7 | 1133 | If em(FILE) is "-" the batch data will be read from standard input. |
c769702f | 1134 | See the "BATCH MODE" section for details. |
6902ed17 | 1135 | |
e40a46de WD |
1136 | dit(bf(-4, --ipv4) or bf(-6, --ipv6)) Tells rsync to prefer IPv4/IPv6 |
1137 | when creating sockets. This only affects sockets that rsync has direct | |
1138 | control over, such as the outgoing socket when directly contacting an | |
c259892c | 1139 | rsync daemon. See also these options in the --daemon mode section. |
e40a46de | 1140 | |
c8d895de WD |
1141 | dit(bf(--checksum-seed=NUM)) Set the MD4 checksum seed to the integer |
1142 | NUM. This 4 byte checksum seed is included in each block and file | |
1143 | MD4 checksum calculation. By default the checksum seed is generated | |
b9f592fb | 1144 | by the server and defaults to the current time(). This option |
c8d895de WD |
1145 | is used to set a specific checksum seed, which is useful for |
1146 | applications that want repeatable block and file checksums, or | |
1147 | in the case where the user wants a more random checksum seed. | |
1148 | Note that setting NUM to 0 causes rsync to use the default of time() | |
b9f592fb | 1149 | for checksum seed. |
c8d895de | 1150 | |
41059f75 AT |
1151 | enddit() |
1152 | ||
bdf278f7 WD |
1153 | The options allowed when starting an rsync daemon are as follows: |
1154 | ||
1155 | startdit() | |
1156 | ||
1157 | dit(bf(--daemon)) This tells rsync that it is to run as a daemon. The | |
1158 | daemon may be accessed using the bf(host::module) or | |
1159 | bf(rsync://host/module/) syntax. | |
1160 | ||
1161 | If standard input is a socket then rsync will assume that it is being | |
1162 | run via inetd, otherwise it will detach from the current terminal and | |
1163 | become a background daemon. The daemon will read the config file | |
1164 | (rsyncd.conf) on each connect made by a client and respond to | |
1165 | requests accordingly. See the rsyncd.conf(5) man page for more | |
1166 | details. | |
1167 | ||
1168 | dit(bf(--address)) By default rsync will bind to the wildcard address | |
1169 | when run as a daemon with the --daemon option or when connecting to a | |
1170 | rsync server. The --address option allows you to specify a specific IP | |
1171 | address (or hostname) to bind to. This makes virtual hosting possible | |
01f8a115 WD |
1172 | in conjunction with the --config option. See also the "address" global |
1173 | option in the rsyncd.conf manpage. | |
bdf278f7 | 1174 | |
1f69bec4 WD |
1175 | dit(bf(--bwlimit=KBPS)) This option allows you to specify a maximum |
1176 | transfer rate in kilobytes per second for the data the daemon sends. | |
1177 | The client can still specify a smaller --bwlimit value, but their | |
1178 | requested value will be rounded down if they try to exceed it. See the | |
1179 | client version of this option (above) for some extra details. | |
1180 | ||
bdf278f7 WD |
1181 | dit(bf(--config=FILE)) This specifies an alternate config file than |
1182 | the default. This is only relevant when --daemon is specified. | |
1183 | The default is /etc/rsyncd.conf unless the daemon is running over | |
1184 | a remote shell program and the remote user is not root; in that case | |
1185 | the default is rsyncd.conf in the current directory (typically $HOME). | |
1186 | ||
1187 | dit(bf(--no-detach)) When running as a daemon, this option instructs | |
1188 | rsync to not detach itself and become a background process. This | |
1189 | option is required when running as a service on Cygwin, and may also | |
1190 | be useful when rsync is supervised by a program such as | |
1191 | bf(daemontools) or AIX's bf(System Resource Controller). | |
1192 | bf(--no-detach) is also recommended when rsync is run under a | |
1193 | debugger. This option has no effect if rsync is run from inetd or | |
1194 | sshd. | |
1195 | ||
c259892c WD |
1196 | dit(bf(--port=PORT)) This specifies an alternate TCP port number for the |
1197 | daemon to listen on rather than the default of 873. See also the "port" | |
1198 | global option in the rsyncd.conf manpage. | |
bdf278f7 | 1199 | |
24b0922b WD |
1200 | dit(bf(-v, --verbose)) This option increases the amount of information the |
1201 | daemon logs during its startup phase. After the client connects, the | |
1202 | daemon's verbosity level will be controlled by the options that the client | |
1203 | used and the "max verbosity" setting in the module's config section. | |
1204 | ||
bdf278f7 WD |
1205 | dit(bf(-4, --ipv4) or bf(-6, --ipv6)) Tells rsync to prefer IPv4/IPv6 |
1206 | when creating the incoming sockets that the rsync daemon will use to | |
1207 | listen for connections. One of these options may be required in older | |
1208 | versions of Linux to work around an IPv6 bug in the kernel (if you see | |
1209 | an "address already in use" error when nothing else is using the port, | |
1210 | try specifying --ipv6 or --ipv4 when starting the daemon). | |
1211 | ||
1212 | dit(bf(-h, --help)) When specified after --daemon, print a short help | |
1213 | page describing the options available for starting an rsync daemon. | |
1214 | ||
1215 | enddit() | |
1216 | ||
16e5de84 | 1217 | manpagesection(FILTER RULES) |
43bd68e5 | 1218 | |
16e5de84 WD |
1219 | The filter rules allow for flexible selection of which files to transfer |
1220 | (include) and which files to skip (exclude). The rules either directly | |
1221 | specify include/exclude patterns or they specify a way to acquire more | |
1222 | include/exclude patterns (e.g. to read them from a file). | |
43bd68e5 | 1223 | |
16e5de84 WD |
1224 | As the list of files/directories to transfer is built, rsync checks each |
1225 | name to be transferred against the list of include/exclude patterns in | |
1226 | turn, and the first matching pattern is acted on: if it is an exclude | |
1227 | pattern, then that file is skipped; if it is an include pattern then that | |
1228 | filename is not skipped; if no matching pattern is found, then the | |
43bd68e5 AT |
1229 | filename is not skipped. |
1230 | ||
16e5de84 WD |
1231 | Rsync builds an ordered list of filter rules as specified on the |
1232 | command-line. Filter rules have the following syntax: | |
1233 | ||
1234 | itemize( | |
1235 | it() x RULE | |
1236 | it() xMODIFIERS RULE | |
1237 | it() ! | |
1238 | ) | |
1239 | ||
1240 | The 'x' is a single-letter that specifies the kind of rule to create. It | |
1241 | can have trailing modifiers, and is separated from the RULE by one of the | |
1242 | following characters: a single space, an equal-sign (=), or an underscore | |
1243 | (_). Here are the available rule prefixes: | |
1244 | ||
1245 | verb( | |
1246 | - specifies an exclude pattern. | |
1247 | + specifies an include pattern. | |
1248 | . specifies a merge-file to read for more rules. | |
1249 | : specifies a per-directory merge-file. | |
1250 | ! clears the current include/exclude list | |
1251 | ) | |
1252 | ||
1253 | Note that the --include/--exclude command-line options do not allow the | |
1254 | full range of rule parsing as described above -- they only allow the | |
1255 | specification of include/exclude patterns and the "!" token (not to | |
1256 | mention the comment lines when reading rules from a file). If a pattern | |
1257 | does not begin with "- " (dash, space) or "+ " (plus, space), then the | |
1258 | rule will be interpreted as if "+ " (for an include option) or "- " (for | |
1259 | an exclude option) were prefixed to the string. A --filter option, on | |
1260 | the other hand, must always contain one of the prefixes above. | |
1261 | ||
1262 | Note also that the --filter, --include, and --exclude options take one | |
1263 | rule/pattern each. To add multiple ones, you can repeat the options on | |
1264 | the command-line, use the merge-file syntax of the --filter option, or | |
1265 | the --include-from/--exclude-from options. | |
1266 | ||
1267 | When rules are being read from a file, empty lines are ignored, as are | |
1268 | comment lines that start with a "#". | |
1269 | ||
1270 | manpagesection(INCLUDE/EXCLUDE PATTERN RULES) | |
1271 | ||
1272 | You can include and exclude files by specifing patterns using the "+" and | |
1273 | "-" filter rules (as introduced in the FILTER RULES section above). These | |
1274 | rules specify a pattern that is matched against the names of the files | |
1275 | that are going to be transferred. These patterns can take several forms: | |
1276 | ||
1277 | itemize( | |
1278 | ||
1279 | it() if the pattern starts with a / then it is anchored to a | |
1280 | particular spot in the hierarchy of files, otherwise it is matched | |
1281 | against the end of the pathname. This is similar to a leading ^ in | |
1282 | regular expressions. | |
1283 | Thus "/foo" would match a file called "foo" at either the "root of the | |
1284 | transfer" (for a global rule) or in the merge-file's directory (for a | |
1285 | per-directory rule). | |
1286 | An unqualified "foo" would match any file or directory named "foo" | |
1287 | anywhere in the tree because the algorithm is applied recursively from | |
1288 | the | |
1289 | top down; it behaves as if each path component gets a turn at being the | |
1290 | end of the file name. Even the unanchored "sub/foo" would match at | |
1291 | any point in the hierarchy where a "foo" was found within a directory | |
1292 | named "sub". See the section on ANCHORING INCLUDE/EXCLUDE PATTERNS for | |
1293 | a full discussion of how to specify a pattern that matches at the root | |
1294 | of the transfer. | |
1295 | ||
1296 | it() if the pattern ends with a / then it will only match a | |
1297 | directory, not a file, link, or device. | |
1298 | ||
1299 | it() if the pattern contains a wildcard character from the set | |
1300 | *?[ then expression matching is applied using the shell filename | |
1301 | matching rules. Otherwise a simple string match is used. | |
1302 | ||
1303 | it() the double asterisk pattern "**" will match slashes while a | |
1304 | single asterisk pattern "*" will stop at slashes. | |
1305 | ||
1306 | it() if the pattern contains a / (not counting a trailing /) or a "**" | |
1307 | then it is matched against the full pathname, including any leading | |
1308 | directories. If the pattern doesn't contain a / or a "**", then it is | |
1309 | matched only against the final component of the filename. | |
1310 | (Remember that the algorithm is applied recursively so "full filename" | |
1311 | can actually be any portion of a path fomr the starting directory on | |
1312 | down.) | |
1313 | ||
1314 | ) | |
1315 | ||
1316 | Note that, when using the --recursive (-r) option (which is implied by | |
1317 | -a), every subcomponent of every path is visited from the top down, so | |
1318 | include/exclude patterns get applied recursively to each subcomponent's | |
1319 | full name (e.g. to include "/foo/bar/baz" the subcomponents "/foo" and | |
1320 | "/foo/bar" must not be excluded). | |
1321 | The exclude patterns actually short-circuit the directory traversal stage | |
1322 | when rsync finds the files to send. If a pattern excludes a particular | |
1323 | parent directory, it can render a deeper include pattern ineffectual | |
1324 | because rsync did not descend through that excluded section of the | |
1325 | hierarchy. This is particularly important when using a trailing '*' rule. | |
1326 | For instance, this won't work: | |
1327 | ||
1328 | verb( | |
1329 | + /some/path/this-file-will-not-be-found | |
1330 | + /file-is-included | |
1331 | - * | |
1332 | ) | |
1333 | ||
1334 | This fails because the parent directory "some" is excluded by the '*' | |
1335 | rule, so rsync never visits any of the files in the "some" or "some/path" | |
1336 | directories. One solution is to ask for all directories in the hierarchy | |
1337 | to be included by using a single rule: "+_*/" (put it somewhere before the | |
1338 | "-_*" rule). Another solution is to add specific include rules for all | |
1339 | the parent dirs that need to be visited. For instance, this set of rules | |
1340 | works fine: | |
1341 | ||
1342 | verb( | |
1343 | + /some/ | |
1344 | + /some/path/ | |
1345 | + /some/path/this-file-is-found | |
1346 | + /file-also-included | |
1347 | - * | |
1348 | ) | |
1349 | ||
1350 | Here are some examples of exclude/include matching: | |
1351 | ||
1352 | itemize( | |
1353 | it() "- *.o" would exclude all filenames matching *.o | |
1354 | it() "- /foo" would exclude a file called foo in the transfer-root directory | |
1355 | it() "- foo/" would exclude any directory called foo | |
1356 | it() "- /foo/*/bar" would exclude any file called bar two | |
1357 | levels below a directory called foo in the transfer-root directory | |
1358 | it() "- /foo/**/bar" would exclude any file called bar two | |
1359 | or more levels below a directory called foo in the transfer-root directory | |
1360 | it() The combination of "+ */", "+ *.c", and "- *" would include all | |
1361 | directories and C source files but nothing else. | |
1362 | it() The combination of "+ foo/", "+ foo/bar.c", and "- *" would include | |
1363 | only the foo directory and foo/bar.c (the foo directory must be | |
1364 | explicitly included or it would be excluded by the "*") | |
1365 | ) | |
1366 | ||
1367 | manpagesection(MERGE-FILE FILTER RULES) | |
1368 | ||
1369 | You can merge whole files into your filter rules by specifying either a | |
1370 | "." or a ":" filter rule (as introduced in the FILTER RULES section | |
1371 | above). | |
1372 | ||
1373 | There are two kinds of merged files -- single-instance ('.') and | |
1374 | per-directory (':'). A single-instance merge file is read one time, and | |
1375 | its rules are incorporated into the filter list in the place of the "." | |
1376 | rule. For per-directory merge files, rsync will scan every directory that | |
1377 | it traverses for the named file, merging its contents when the file exists | |
1378 | into the current list of inherited rules. These per-directory rule files | |
1379 | must be created on the sending side because it is the sending side that is | |
1380 | being scanned for the available files to transfer. These rule files may | |
1381 | also need to be transferred to the receiving side if you want them to | |
1382 | affect what files don't get deleted (see PER-DIRECTORY RULES AND DELETE | |
1383 | below). | |
1384 | ||
1385 | Some examples: | |
1386 | ||
1387 | verb( | |
1388 | . /etc/rsync/default.rules | |
1389 | : .per-dir-filter | |
1390 | :n- .non-inherited-per-dir-excludes | |
1391 | ) | |
1392 | ||
1393 | The following modifiers are accepted after the "." or ":": | |
1394 | ||
1395 | itemize( | |
1396 | it() A "-" specifies that the file should consist of only exclude | |
1397 | patterns, with no other rule-parsing except for the list-clearing | |
1398 | token ("!"). | |
1399 | ||
1400 | it() A "+" specifies that the file should consist of only include | |
1401 | patterns, with no other rule-parsing except for the list-clearing | |
1402 | token ("!"). | |
1403 | ||
1404 | it() A "C" is a shorthand for the modifiers "sn-", which makes the | |
1405 | parsing compatible with the way CVS parses their exclude files. If no | |
1406 | filename is specified, ".cvsignore" is assumed. | |
1407 | ||
1408 | it() A "e" will exclude the merge-file from the transfer; e.g. | |
1409 | ":e_.rules" is like ":_.rules" and "-_.rules". | |
1410 | ||
1411 | it() An "n" specifies that the rules are not inherited by subdirectories. | |
1412 | ||
1413 | it() An "s" specifies that the rules are split on all whitespace instead | |
1414 | of the normal line-splitting. This also turns off comments. Note: the | |
1415 | space that separates the prefix from the rule is treated specially, so | |
1416 | "- foo + bar" is parsed as two rules (assuming that "-" or "+" was not | |
1417 | specified to turn off the parsing of prefixes). | |
1418 | ) | |
1419 | ||
1420 | Per-directory rules are inherited in all subdirectories of the directory | |
1421 | where the merge-file was found unless the 'n' modifier was used. Each | |
1422 | subdirectory's rules are prefixed to the inherited per-directory rules | |
1423 | from its parents, which gives the newest rules a higher priority than the | |
1424 | inherited rules. The entire set of per-dir rules is grouped together in | |
1425 | the spot where the merge-file was specified, so it is possible to override | |
1426 | per-dir rules via a rule that got specified earlier in the list of global | |
1427 | rules. When the list-clearing rule ("!") is read from a per-directory | |
1428 | file, it only clears the inherited rules for the current merge file. | |
1429 | ||
1430 | Another way to prevent a single per-dir rule from being inherited is to | |
1431 | anchor it with a leading slash. Anchored rules in a per-directory | |
1432 | merge-file are relative to the merge-file's directory, so a pattern "/foo" | |
1433 | would only match the file "foo" in the directory where the per-dir filter | |
1434 | file was found. | |
1435 | ||
1436 | Here's an example filter file which you'd specify via --filter=". file": | |
1437 | ||
1438 | verb( | |
1439 | . /home/user/.global-filter | |
1440 | - *.gz | |
1441 | : .rules | |
1442 | + *.[ch] | |
1443 | - *.o | |
1444 | ) | |
1445 | ||
1446 | This will merge the contents of the /home/user/.global-filter file at the | |
1447 | start of the list and also turns the ".rules" filename into a per-directory | |
1448 | filter file. All rules read-in prior to the start of the directory scan | |
1449 | follow the global anchoring rules (i.e. a leading slash matches at the root | |
1450 | of the transfer). | |
1451 | ||
1452 | If a per-directory merge-file is specified with a path that is a parent | |
1453 | directory of the first transfer directory, rsync will scan all the parent | |
1454 | dirs from that starting point to the transfer directory for the indicated | |
1455 | per-directory file. For instance, here is a common filter (see -F): | |
1456 | ||
1457 | verb( | |
1458 | --filter=': /.rsync-filter' | |
1459 | ) | |
1460 | ||
1461 | That rule tells rsync to scan for the file .rsync-filter in all | |
1462 | directories from the root down through the parent directory of the | |
1463 | transfer prior to the start of the normal directory scan of the file in | |
1464 | the directories that are sent as a part of the transfer. (Note: for an | |
1465 | rsync daemon, the root is always the same as the module's "path".) | |
1466 | ||
1467 | Some examples of this pre-scanning for per-directory files: | |
1468 | ||
1469 | verb( | |
1470 | rsync -avF /src/path/ /dest/dir | |
1471 | rsync -av --filter=': ../../.rsync-filter' /src/path/ /dest/dir | |
1472 | rsync -av --fitler=': .rsync-filter' /src/path/ /dest/dir | |
1473 | ) | |
1474 | ||
1475 | The first two commands above will look for ".rsync-filter" in "/" and | |
1476 | "/src" before the normal scan begins looking for the file in "/src/path" | |
1477 | and its subdirectories. The last command avoids the parent-dir scan | |
1478 | and only looks for the ".rsync-filter" files in each directory that is | |
1479 | a part of the transfer. | |
1480 | ||
1481 | If you want to include the contents of a ".cvsignore" in your patterns, | |
1482 | you should use the rule ":C" -- this is a short-hand for the rule | |
1483 | ":sn-_.cvsignore", and ensures that the .cvsignore file's contents are | |
1484 | interpreted according to the same parsing rules that CVS uses. You can | |
1485 | use this to affect where the --cvs-exclude (-C) option's inclusion of the | |
1486 | per-directory .cvsignore file gets placed into your rules by putting a | |
1487 | ":C" wherever you like in your filter rules. Without this, rsync would | |
1488 | add the per-dir rule for the .cvignore file at the end of all your other | |
1489 | rules (giving it a lower priority than your command-line rules). For | |
1490 | example: | |
1491 | ||
1492 | verb( | |
1493 | cat <<EOT | rsync -avC --filter='. -' a/ b | |
1494 | + foo.o | |
1495 | :C | |
1496 | - *.old | |
1497 | EOT | |
1498 | ||
1499 | rsync -avC --include=foo.o -f :C --exclude='*.old' a/ b | |
1500 | ) | |
1501 | ||
1502 | Both of the above rsync commands are identical. Each one will merge all | |
1503 | the per-directory .cvsignore rules in the middle of the list rather than | |
1504 | at the end. This allows their dir-specific rules to supersede the rules | |
1505 | that follow the :C instead of being subservient to all your rules. (The | |
1506 | global rules taken from the $HOME/.cvsignore file and from $CVSIGNORE are | |
1507 | not repositioned from their spot at the end of your rules, however -- feel | |
1508 | free to manually include $HOME/.cvsignore elsewhere in your rules.) | |
1509 | ||
1510 | manpagesection(LIST-CLEARING FILTER RULE) | |
1511 | ||
1512 | You can clear the current include/exclude list by using the "!" filter | |
1513 | rule (as introduced in the FILTER RULES section above). The "current" | |
1514 | list is either the global list of rules (if the rule is encountered while | |
1515 | parsing the filter options) or a set of per-directory rules (which are | |
1516 | inherited in their own sub-list, so a subdirectory can use this to clear | |
1517 | out the parent's rules). | |
1518 | ||
1519 | manpagesection(ANCHORING INCLUDE/EXCLUDE PATTERNS) | |
1520 | ||
1521 | As mentioned earlier, global include/exclude patterns are anchored at the | |
1522 | "root of the transfer" (as opposed to per-directory patterns, which are | |
1523 | anchored at the merge-file's directory). If you think of the transfer as | |
1524 | a subtree of names that are being sent from sender to receiver, the | |
1525 | transfer-root is where the tree starts to be duplicated in the destination | |
1526 | directory. This root governs where patterns that start with a / match. | |
a4b6f305 WD |
1527 | |
1528 | Because the matching is relative to the transfer-root, changing the | |
20af605e | 1529 | trailing slash on a source path or changing your use of the --relative |
a4b6f305 WD |
1530 | option affects the path you need to use in your matching (in addition to |
1531 | changing how much of the file tree is duplicated on the destination | |
16e5de84 | 1532 | host). The following examples demonstrate this. |
a4b6f305 | 1533 | |
b5ebe6d9 WD |
1534 | Let's say that we want to match two source files, one with an absolute |
1535 | path of "/home/me/foo/bar", and one with a path of "/home/you/bar/baz". | |
1536 | Here is how the various command choices differ for a 2-source transfer: | |
a4b6f305 WD |
1537 | |
1538 | verb( | |
b5ebe6d9 | 1539 | Example cmd: rsync -a /home/me /home/you /dest |
a4b6f305 | 1540 | +/- pattern: /me/foo/bar |
b5ebe6d9 | 1541 | +/- pattern: /you/bar/baz |
a4b6f305 | 1542 | Target file: /dest/me/foo/bar |
b5ebe6d9 | 1543 | Target file: /dest/you/bar/baz |
a4b6f305 | 1544 | |
b5ebe6d9 | 1545 | Example cmd: rsync -a /home/me/ /home/you/ /dest |
b5ebe6d9 WD |
1546 | +/- pattern: /foo/bar (note missing "me") |
1547 | +/- pattern: /bar/baz (note missing "you") | |
a4b6f305 | 1548 | Target file: /dest/foo/bar |
b5ebe6d9 | 1549 | Target file: /dest/bar/baz |
a4b6f305 | 1550 | |
b5ebe6d9 | 1551 | Example cmd: rsync -a --relative /home/me/ /home/you /dest |
b5ebe6d9 WD |
1552 | +/- pattern: /home/me/foo/bar (note full path) |
1553 | +/- pattern: /home/you/bar/baz (ditto) | |
a4b6f305 | 1554 | Target file: /dest/home/me/foo/bar |
b5ebe6d9 | 1555 | Target file: /dest/home/you/bar/baz |
be92ac6c | 1556 | |
b5ebe6d9 | 1557 | Example cmd: cd /home; rsync -a --relative me/foo you/ /dest |
b5ebe6d9 WD |
1558 | +/- pattern: /me/foo/bar (starts at specified path) |
1559 | +/- pattern: /you/bar/baz (ditto) | |
be92ac6c | 1560 | Target file: /dest/me/foo/bar |
b5ebe6d9 | 1561 | Target file: /dest/you/bar/baz |
a4b6f305 WD |
1562 | ) |
1563 | ||
16e5de84 | 1564 | The easiest way to see what name you should filter is to just |
a4b6f305 WD |
1565 | look at the output when using --verbose and put a / in front of the name |
1566 | (use the --dry-run option if you're not yet ready to copy any files). | |
d1cce1dd | 1567 | |
16e5de84 | 1568 | manpagesection(PER-DIRECTORY RULES AND DELETE) |
43bd68e5 | 1569 | |
16e5de84 WD |
1570 | Without a delete option, per-directory rules are only relevant on the |
1571 | sending side, so you can feel free to exclude the merge files themselves | |
1572 | without affecting the transfer. To make this easy, the 'e' modifier adds | |
1573 | this exclude for you, as seen in these two equivalent commands: | |
27b9a19b | 1574 | |
16e5de84 WD |
1575 | verb( |
1576 | rsync -av --filter=': .excl' --exclude=.excl host:src/dir /dest | |
1577 | rsync -av --filter=':e .excl' host:src/dir /dest | |
43bd68e5 AT |
1578 | ) |
1579 | ||
16e5de84 WD |
1580 | However, if you want to do a delete on the receiving side AND you want some |
1581 | files to be excluded from being deleted, you'll need to be sure that the | |
1582 | receiving side knows what files to exclude. The easiest way is to include | |
1583 | the per-directory merge files in the transfer and use --delete-after, | |
1584 | because this ensures that the receiving side gets all the same exclude | |
1585 | rules as the sending side before it tries to delete anything: | |
43bd68e5 | 1586 | |
20af605e | 1587 | verb( |
16e5de84 | 1588 | rsync -avF --delete-after host:src/dir /dest |
20af605e WD |
1589 | ) |
1590 | ||
16e5de84 WD |
1591 | However, if the merge files are not a part of the transfer, you'll need to |
1592 | either specify some global exclude rules (i.e. specified on the command | |
1593 | line), or you'll need to maintain your own per-directory merge files on | |
1594 | the receiving side. An example of the first is this (assume that the | |
1595 | remote .rules files exclude themselves): | |
20af605e WD |
1596 | |
1597 | verb( | |
16e5de84 WD |
1598 | rsync -av --filter=': .rules' --filter='. /my/extra.rules' |
1599 | --delete host:src/dir /dest | |
20af605e WD |
1600 | ) |
1601 | ||
16e5de84 WD |
1602 | In the above example the extra.rules file can affect both sides of the |
1603 | transfer, but (on the sending side) the rules are subservient to the rules | |
1604 | merged from the .rules files because they were specified after the | |
1605 | per-directory merge rule. | |
43bd68e5 | 1606 | |
16e5de84 WD |
1607 | In one final example, the remote side is excluding the .rsync-filter |
1608 | files from the transfer, but we want to use our own .rsync-filter files | |
1609 | to control what gets deleted on the receiving side. To do this we must | |
1610 | specifically exclude the per-directory merge files (so that they don't get | |
1611 | deleted) and then put rules into the local files to control what else | |
1612 | should not get deleted. Like one of these commands: | |
1613 | ||
1614 | verb( | |
1615 | rsync -av --filter=':e /.rsync-filter' --delete host:src/dir /dest | |
1616 | rsync -avFF --delete host:src/dir /dest | |
43bd68e5 AT |
1617 | ) |
1618 | ||
6902ed17 MP |
1619 | manpagesection(BATCH MODE) |
1620 | ||
2e3c1417 | 1621 | bf(Note:) Batch mode should be considered experimental in this version |
7432ccf4 WD |
1622 | of rsync. The interface and behavior have now stabilized, though, so |
1623 | feel free to try this out. | |
088aac85 DD |
1624 | |
1625 | Batch mode can be used to apply the same set of updates to many | |
1626 | identical systems. Suppose one has a tree which is replicated on a | |
1627 | number of hosts. Now suppose some changes have been made to this | |
1628 | source tree and those changes need to be propagated to the other | |
1629 | hosts. In order to do this using batch mode, rsync is run with the | |
1630 | write-batch option to apply the changes made to the source tree to one | |
1631 | of the destination trees. The write-batch option causes the rsync | |
b9f592fb WD |
1632 | client to store in a "batch file" all the information needed to repeat |
1633 | this operation against other, identical destination trees. | |
1634 | ||
1635 | To apply the recorded changes to another destination tree, run rsync | |
1636 | with the read-batch option, specifying the name of the same batch | |
1637 | file, and the destination tree. Rsync updates the destination tree | |
1638 | using the information stored in the batch file. | |
1639 | ||
1640 | For convenience, one additional file is creating when the write-batch | |
1641 | option is used. This file's name is created by appending | |
73e01568 | 1642 | ".sh" to the batch filename. The .sh file contains |
b9f592fb WD |
1643 | a command-line suitable for updating a destination tree using that |
1644 | batch file. It can be executed using a Bourne(-like) shell, optionally | |
1645 | passing in an alternate destination tree pathname which is then used | |
1646 | instead of the original path. This is useful when the destination tree | |
1647 | path differs from the original destination tree path. | |
1648 | ||
1649 | Generating the batch file once saves having to perform the file | |
1650 | status, checksum, and data block generation more than once when | |
088aac85 | 1651 | updating multiple destination trees. Multicast transport protocols can |
b9f592fb WD |
1652 | be used to transfer the batch update files in parallel to many hosts |
1653 | at once, instead of sending the same data to every host individually. | |
088aac85 | 1654 | |
4602eafa | 1655 | Examples: |
088aac85 DD |
1656 | |
1657 | verb( | |
98f51bfb WD |
1658 | $ rsync --write-batch=foo -a host:/source/dir/ /adest/dir/ |
1659 | $ scp foo* remote: | |
1660 | $ ssh remote ./foo.sh /bdest/dir/ | |
4602eafa WD |
1661 | ) |
1662 | ||
1663 | verb( | |
98f51bfb WD |
1664 | $ rsync --write-batch=foo -a /source/dir/ /adest/dir/ |
1665 | $ ssh remote rsync --read-batch=- -a /bdest/dir/ <foo | |
4602eafa WD |
1666 | ) |
1667 | ||
98f51bfb WD |
1668 | In these examples, rsync is used to update /adest/dir/ from /source/dir/ |
1669 | and the information to repeat this operation is stored in "foo" and | |
1670 | "foo.sh". The host "remote" is then updated with the batched data going | |
1671 | into the directory /bdest/dir. The differences between the two examples | |
1672 | reveals some of the flexibility you have in how you deal with batches: | |
1673 | ||
1674 | itemize( | |
1675 | ||
1676 | it() The first example shows that the initial copy doesn't have to be | |
1677 | local -- you can push or pull data to/from a remote host using either the | |
1678 | remote-shell syntax or rsync daemon syntax, as desired. | |
6902ed17 | 1679 | |
98f51bfb WD |
1680 | it() The first example uses the created "foo.sh" file to get the right |
1681 | rsync options when running the read-batch command on the remote host. | |
1682 | ||
1683 | it() The second example reads the batch data via standard input so that | |
1684 | the batch file doesn't need to be copied to the remote machine first. | |
1685 | This example avoids the foo.sh script because it needed to use a modified | |
1686 | --read-batch option, but you could edit the script file if you wished to | |
1687 | make use of it (just be sure that no other option is trying to use | |
1688 | standard input, such as the "--exclude-from=-" option). | |
1689 | ||
1690 | ) | |
088aac85 DD |
1691 | |
1692 | Caveats: | |
1693 | ||
98f51bfb | 1694 | The read-batch option expects the destination tree that it is updating |
088aac85 DD |
1695 | to be identical to the destination tree that was used to create the |
1696 | batch update fileset. When a difference between the destination trees | |
7432ccf4 WD |
1697 | is encountered the update might be discarded with no error (if the file |
1698 | appears to be up-to-date already) or the file-update may be attempted | |
1699 | and then, if the file fails to verify, the update discarded with an | |
1700 | error. This means that it should be safe to re-run a read-batch operation | |
59d73bf3 | 1701 | if the command got interrupted. If you wish to force the batched-update to |
7432ccf4 | 1702 | always be attempted regardless of the file's size and date, use the -I |
59d73bf3 WD |
1703 | option (when reading the batch). |
1704 | If an error occurs, the destination tree will probably be in a | |
7432ccf4 | 1705 | partially updated state. In that case, rsync can |
088aac85 DD |
1706 | be used in its regular (non-batch) mode of operation to fix up the |
1707 | destination tree. | |
1708 | ||
b9f592fb | 1709 | The rsync version used on all destinations must be at least as new as the |
59d73bf3 WD |
1710 | one used to generate the batch file. Rsync will die with an error if the |
1711 | protocol version in the batch file is too new for the batch-reading rsync | |
1712 | to handle. | |
088aac85 | 1713 | |
98f51bfb | 1714 | The --dry-run (-n) option does not work in batch mode and yields a runtime |
088aac85 DD |
1715 | error. |
1716 | ||
7432ccf4 WD |
1717 | When reading a batch file, rsync will force the value of certain options |
1718 | to match the data in the batch file if you didn't set them to the same | |
1719 | as the batch-writing command. Other options can (and should) be changed. | |
1720 | For instance | |
b9f592fb WD |
1721 | --write-batch changes to --read-batch, --files-from is dropped, and the |
1722 | --include/--exclude options are not needed unless --delete is specified | |
7432ccf4 | 1723 | without --delete-excluded. |
b9f592fb | 1724 | |
98f51bfb WD |
1725 | The code that creates the BATCH.sh file transforms any include/exclude |
1726 | options into a single list that is appended as a "here" document to the | |
1727 | shell script file. An advanced user can use this to modify the exclude | |
1728 | list if a change in what gets deleted by --delete is desired. A normal | |
1729 | user can ignore this detail and just use the shell script as an easy way | |
1730 | to run the appropriate --read-batch command for the batched data. | |
1731 | ||
59d73bf3 WD |
1732 | The original batch mode in rsync was based on "rsync+", but the latest |
1733 | version uses a new implementation. | |
6902ed17 | 1734 | |
eb06fa95 MP |
1735 | manpagesection(SYMBOLIC LINKS) |
1736 | ||
f28bd833 | 1737 | Three basic behaviors are possible when rsync encounters a symbolic |
eb06fa95 MP |
1738 | link in the source directory. |
1739 | ||
1740 | By default, symbolic links are not transferred at all. A message | |
1741 | "skipping non-regular" file is emitted for any symlinks that exist. | |
1742 | ||
1743 | If bf(--links) is specified, then symlinks are recreated with the same | |
1744 | target on the destination. Note that bf(--archive) implies | |
1745 | bf(--links). | |
1746 | ||
1747 | If bf(--copy-links) is specified, then symlinks are "collapsed" by | |
1748 | copying their referent, rather than the symlink. | |
1749 | ||
1750 | rsync also distinguishes "safe" and "unsafe" symbolic links. An | |
1751 | example where this might be used is a web site mirror that wishes | |
1752 | ensure the rsync module they copy does not include symbolic links to | |
1753 | bf(/etc/passwd) in the public section of the site. Using | |
1754 | bf(--copy-unsafe-links) will cause any links to be copied as the file | |
1755 | they point to on the destination. Using bf(--safe-links) will cause | |
4d888108 | 1756 | unsafe links to be omitted altogether. |
eb06fa95 | 1757 | |
7bd0cf5b MP |
1758 | Symbolic links are considered unsafe if they are absolute symlinks |
1759 | (start with bf(/)), empty, or if they contain enough bf("..") | |
1760 | components to ascend from the directory being copied. | |
1761 | ||
d310a212 AT |
1762 | manpagesection(DIAGNOSTICS) |
1763 | ||
14d43f1f | 1764 | rsync occasionally produces error messages that may seem a little |
d310a212 AT |
1765 | cryptic. The one that seems to cause the most confusion is "protocol |
1766 | version mismatch - is your shell clean?". | |
1767 | ||
1768 | This message is usually caused by your startup scripts or remote shell | |
1769 | facility producing unwanted garbage on the stream that rsync is using | |
14d43f1f | 1770 | for its transport. The way to diagnose this problem is to run your |
d310a212 AT |
1771 | remote shell like this: |
1772 | ||
1773 | verb( | |
43cd760f | 1774 | ssh remotehost /bin/true > out.dat |
d310a212 AT |
1775 | ) |
1776 | ||
1777 | then look at out.dat. If everything is working correctly then out.dat | |
2cfeab21 | 1778 | should be a zero length file. If you are getting the above error from |
d310a212 AT |
1779 | rsync then you will probably find that out.dat contains some text or |
1780 | data. Look at the contents and try to work out what is producing | |
14d43f1f | 1781 | it. The most common cause is incorrectly configured shell startup |
d310a212 AT |
1782 | scripts (such as .cshrc or .profile) that contain output statements |
1783 | for non-interactive logins. | |
1784 | ||
16e5de84 | 1785 | If you are having trouble debugging filter patterns, then |
e6c64e79 MP |
1786 | try specifying the -vv option. At this level of verbosity rsync will |
1787 | show why each individual file is included or excluded. | |
1788 | ||
55b64e4b MP |
1789 | manpagesection(EXIT VALUES) |
1790 | ||
1791 | startdit() | |
a73de5f3 WD |
1792 | dit(bf(0)) Success |
1793 | dit(bf(1)) Syntax or usage error | |
1794 | dit(bf(2)) Protocol incompatibility | |
1795 | dit(bf(3)) Errors selecting input/output files, dirs | |
1796 | dit(bf(4)) Requested action not supported: an attempt | |
8212336a | 1797 | was made to manipulate 64-bit files on a platform that cannot support |
f28bd833 | 1798 | them; or an option was specified that is supported by the client and |
8212336a | 1799 | not by the server. |
a73de5f3 | 1800 | dit(bf(5)) Error starting client-server protocol |
b5accaba WD |
1801 | dit(bf(10)) Error in socket I/O |
1802 | dit(bf(11)) Error in file I/O | |
a73de5f3 WD |
1803 | dit(bf(12)) Error in rsync protocol data stream |
1804 | dit(bf(13)) Errors with program diagnostics | |
1805 | dit(bf(14)) Error in IPC code | |
1806 | dit(bf(20)) Received SIGUSR1 or SIGINT | |
1807 | dit(bf(21)) Some error returned by waitpid() | |
1808 | dit(bf(22)) Error allocating core memory buffers | |
3c1e2ad9 WD |
1809 | dit(bf(23)) Partial transfer due to error |
1810 | dit(bf(24)) Partial transfer due to vanished source files | |
a73de5f3 | 1811 | dit(bf(30)) Timeout in data send/receive |
55b64e4b MP |
1812 | enddit() |
1813 | ||
de2fd20e AT |
1814 | manpagesection(ENVIRONMENT VARIABLES) |
1815 | ||
1816 | startdit() | |
1817 | ||
1818 | dit(bf(CVSIGNORE)) The CVSIGNORE environment variable supplements any | |
1819 | ignore patterns in .cvsignore files. See the --cvs-exclude option for | |
1820 | more details. | |
1821 | ||
1822 | dit(bf(RSYNC_RSH)) The RSYNC_RSH environment variable allows you to | |
ea7f8108 WD |
1823 | override the default shell used as the transport for rsync. Command line |
1824 | options are permitted after the command name, just as in the -e option. | |
de2fd20e | 1825 | |
4c3b4b25 AT |
1826 | dit(bf(RSYNC_PROXY)) The RSYNC_PROXY environment variable allows you to |
1827 | redirect your rsync client to use a web proxy when connecting to a | |
1828 | rsync daemon. You should set RSYNC_PROXY to a hostname:port pair. | |
1829 | ||
de2fd20e | 1830 | dit(bf(RSYNC_PASSWORD)) Setting RSYNC_PASSWORD to the required |
bb18e755 | 1831 | password allows you to run authenticated rsync connections to an rsync |
de2fd20e AT |
1832 | daemon without user intervention. Note that this does not supply a |
1833 | password to a shell transport such as ssh. | |
1834 | ||
1835 | dit(bf(USER) or bf(LOGNAME)) The USER or LOGNAME environment variables | |
bb18e755 | 1836 | are used to determine the default username sent to an rsync server. |
4b2f6a7c | 1837 | If neither is set, the username defaults to "nobody". |
de2fd20e | 1838 | |
14d43f1f | 1839 | dit(bf(HOME)) The HOME environment variable is used to find the user's |
de2fd20e AT |
1840 | default .cvsignore file. |
1841 | ||
1842 | enddit() | |
1843 | ||
41059f75 AT |
1844 | manpagefiles() |
1845 | ||
30e8c8e1 | 1846 | /etc/rsyncd.conf or rsyncd.conf |
41059f75 AT |
1847 | |
1848 | manpageseealso() | |
1849 | ||
1850 | rsyncd.conf(5) | |
1851 | ||
1852 | manpagediagnostics() | |
1853 | ||
1854 | manpagebugs() | |
1855 | ||
1856 | times are transferred as unix time_t values | |
1857 | ||
f28bd833 | 1858 | When transferring to FAT filesystems rsync may re-sync |
38843171 DD |
1859 | unmodified files. |
1860 | See the comments on the --modify-window option. | |
1861 | ||
b5accaba | 1862 | file permissions, devices, etc. are transferred as native numerical |
41059f75 AT |
1863 | values |
1864 | ||
a87b3b2a | 1865 | see also the comments on the --delete option |
41059f75 | 1866 | |
38843171 DD |
1867 | Please report bugs! See the website at |
1868 | url(http://rsync.samba.org/)(http://rsync.samba.org/) | |
41059f75 AT |
1869 | |
1870 | manpagesection(CREDITS) | |
1871 | ||
1872 | rsync is distributed under the GNU public license. See the file | |
1873 | COPYING for details. | |
1874 | ||
41059f75 | 1875 | A WEB site is available at |
3cd5eb3b MP |
1876 | url(http://rsync.samba.org/)(http://rsync.samba.org/). The site |
1877 | includes an FAQ-O-Matic which may cover questions unanswered by this | |
1878 | manual page. | |
9e3c856a AT |
1879 | |
1880 | The primary ftp site for rsync is | |
1881 | url(ftp://rsync.samba.org/pub/rsync)(ftp://rsync.samba.org/pub/rsync). | |
41059f75 AT |
1882 | |
1883 | We would be delighted to hear from you if you like this program. | |
1884 | ||
9e3c856a AT |
1885 | This program uses the excellent zlib compression library written by |
1886 | Jean-loup Gailly and Mark Adler. | |
41059f75 AT |
1887 | |
1888 | manpagesection(THANKS) | |
1889 | ||
1890 | Thanks to Richard Brent, Brendan Mackay, Bill Waite, Stephen Rothwell | |
7ff701e8 MP |
1891 | and David Bell for helpful suggestions, patches and testing of rsync. |
1892 | I've probably missed some people, my apologies if I have. | |
1893 | ||
ce5f2732 | 1894 | Especial thanks also to: David Dykstra, Jos Backus, Sebastian Krahmer, |
98f51bfb | 1895 | Martin Pool, Wayne Davison, J.W. Schultz. |
41059f75 AT |
1896 | |
1897 | manpageauthor() | |
1898 | ||
ce5f2732 MP |
1899 | rsync was originally written by Andrew Tridgell and Paul Mackerras. |
1900 | Many people have later contributed to it. | |
3cd5eb3b | 1901 | |
a5d74a18 | 1902 | Mailing lists for support and development are available at |
7ff701e8 | 1903 | url(http://lists.samba.org)(lists.samba.org) |