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