Print this page
6198 Let's EOL cachefs
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man1/filesync.1
+++ new/usr/src/man/man1/filesync.1
1 1 '\" te
2 2 .\" Copyright (c) 1998 Sun Microsystems, Inc. All Rights Reserved.
3 +.\" Copyright 2015 Nexenta Systems, Inc. All rights reserved.
3 4 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 5 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 6 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 -.TH FILESYNC 1 "Nov 6, 2000"
7 +.TH FILESYNC 1 "Sep 8, 2015"
7 8 .SH NAME
8 9 filesync \- synchronize ordinary, directory or special files
9 10 .SH SYNOPSIS
10 11 .LP
11 12 .nf
12 13 \fBfilesync\fR [\fB-aehmnqvy\fR] [\fB-o\fR src | dst]
13 14 [\fB-f\fR src | dst | old | new] [\fB-r\fR \fIdirectory\fR]...
14 15 .fi
15 16
16 17 .LP
17 18 .nf
18 19 \fBfilesync\fR [\fB-aehmnqvy\fR] \fB-s\fR \fIsource-dir\fR \fB-d\fR \fIdest-dir\fR \fIfilename\fR...
19 20 .fi
20 21
21 22 .SH DESCRIPTION
22 23 .sp
23 24 .LP
24 25 The \fBfilesync\fR utility \fIsynchronizes\fR files between multiple computer
25 26 systems, typically a server and a portable computer. \fBfilesync\fR
26 27 synchronizes ordinary, directory or special files. Although intended for use on
27 28 nomadic systems, \fBfilesync\fR is useful for backup and file replication on
28 29 more permanently connected systems.
29 30 .sp
30 31 .LP
31 32 If files are synchronized between systems, the corresponding files on each of
32 33 the systems are \fIidentical\fR. Changing a file on one or both of the systems
|
↓ open down ↓ |
16 lines elided |
↑ open up ↑ |
33 34 causes the files to become different (not synchronized). In order to make the
34 35 files identical again, the differences between the files must be
35 36 \fIreconciled\fR. See \fBReconciling and Synchronizing Files\fR for specific
36 37 details about how \fBfilesync\fR reconciles and synchronizes files.
37 38 .sp
38 39 .LP
39 40 There are two forms of the \fBfilesync\fR command. The first form of
40 41 \fBfilesync\fR is invoked without file arguments. This form of \fBfilesync\fR
41 42 reconciles differences between the files and systems specified in the
42 43 \fB$HOME/.packingrules\fR file. \fB$HOME/.packingrules\fR is a packing rules
43 -list for \fBfilesync\fR and \fBcachefspack\fR, and contains a list of files to
44 -be kept synchronized. See \fBpackingrules\fR(4) and \fBcachefspack\fR(1M).
44 +list for \fBfilesync\fR and contains a list of files to
45 +be kept synchronized. See \fBpackingrules\fR(4).
45 46 .sp
46 47 .LP
47 48 The second form of \fBfilesync\fR copies specific files from a directory on the
48 49 source system to a directory on the destination system. In addition, this form
49 50 of \fBfilesync\fR adds the file or files specified as arguments
50 51 (\fIfilename\fR) to \fB$HOME/.packingrules\fR. See \fB-s\fR and \fB-d\fR for
51 52 information about specifying directories on source and destination systems. See
52 53 \fBOPERANDS\fR for details about specifying file (\fIfilename\fR) arguments.
53 54 .sp
54 55 .LP
55 56 Multiple \fBfilesync\fR commands are cumulative (that is, the specified files
56 57 are added to the already existing packing rules file list). See \fBMultiple
57 58 filesync Commands\fR.
58 59 .SS "Reconciling and Synchronizing Files"
59 60 .sp
60 61 .LP
61 62 \fBfilesync\fR synchronizes files between computer systems by performing the
62 63 following two tasks:
63 64 .RS +4
64 65 .TP
65 66 1.
66 67 \fBfilesync\fR examines the directories and files specified in the packing
67 68 rules file on both systems, and determines whether or not they are identical.
68 69 Any file that differs requires reconciliation.
69 70 .sp
70 71 \fBfilesync\fR also maintains a baseline summary in the
71 72 \fB$HOME/.filesync-base\fR file for all of the files that are being monitored.
72 73 This file lists the names, types, and sizes of all files as of the last
73 74 reconciliation.
74 75 .RE
75 76 .RS +4
76 77 .TP
77 78 2.
78 79 Based on the information contained in the baseline file and the specified
79 80 options (see \fBResolving filesync Conflicts\fR), \fBfilesync\fR determines
80 81 which of the various copies is the correct one, and makes the corresponding
81 82 changes to the other system. Once this has been done, the two copies are,
82 83 again, identical (synchronized).
83 84 .sp
84 85 If a source file has changed and the destination file has not, the changes on
85 86 the source system are propagated to the destination system. If a destination
86 87 file has changed and the corresponding source file has not, the changes on the
87 88 destination file are propagated to the source system. If both systems have
88 89 changed (and the files are not still identical) a warning message will be
89 90 printed out, asking the user to resolve the conflict manually. See
90 91 \fBResolving filesync Conflicts\fR.
91 92 .RE
92 93 .SS "Resolving filesync Conflicts"
93 94 .sp
94 95 .LP
95 96 In cases where files on both sides have changed, \fBfilesync\fR attempts to
96 97 determine which version should be chosen. If \fBfilesync\fR cannot
97 98 automatically determine which version should be selected, it prints out a
98 99 warning message and leaves the two incompatible versions of the file
99 100 unreconciled.
100 101 .sp
101 102 .LP
102 103 In these cases, you must either resolve the differences manually, or tell
103 104 \fBfilesync\fR how to choose which file should win. Use the \fB-o\fR and
104 105 \fB-f\fR options to tell \fBfilesync\fR how to resolve conflicts (see
105 106 \fBOPTIONS\fR).
106 107 .sp
107 108 .LP
108 109 Alternatively, for each conflicting file, you can examine the two versions,
109 110 determine which one should be kept, and manually bring the two versions into
110 111 agreement (by copying, deleting, or changing the ownership or protection to be
111 112 correct). You can then re-run \fBfilesync\fR to see whether or not any other
112 113 conflicts remain.
113 114 .SS "Packing Rules File"
114 115 .sp
115 116 .LP
116 117 The packing rules file \fB$HOME/.packingrules\fR contains a list of files to be
117 118 kept synchronized. The syntax of this file is described in
118 119 \fBpackingrules\fR(4).
119 120 .sp
120 121 .LP
121 122 The \fB$HOME/.packingrules\fR file is automatically created if users invoke
122 123 \fBfilesync\fR with filename arguments. By using \fBfilesync\fR options, users
123 124 can augment the packing rules in \fB$HOME/.packingrules\fR.
124 125 .sp
125 126 .LP
126 127 Many users choose to create the packing rules file manually and edit it by
127 128 hand. Users can edit \fB$HOME/.packingrules\fR (using any editor) to
128 129 permanently change the \fB$HOME/.packingrules\fR file, or to gain access to
129 130 more powerful options that are not available from the command line (such as
130 131 \fBIGNORE\fR commands). It is much easier to enter complex wildcard expressions
131 132 by editing the \fB$HOME/.packingrules\fR file.
132 133 .SS "Baseline File"
133 134 .sp
134 135 .LP
135 136 \fB$HOME/.filesync-base\fR is the \fBfilesync\fR baseline summary file.
136 137 \fBfilesync\fR uses the information in \fB$HOME/.filesync-base\fR to identify
137 138 the differences between files during the reconciliation and synchronization
138 139 process. Users do not create or edit the baseline file. It is created
139 140 automatically by \fBfilesync\fR and records the last known state of agreement
140 141 between all of the files being maintained.
141 142 .SS "Multiple filesync Commands"
142 143 .sp
143 144 .LP
144 145 Over a period of time, the set of files you want to keep synchronized can
145 146 change. It is common, for instance, to want to keep files pertaining to only a
146 147 few active projects on your notebook. If you continue to keep files associated
147 148 with every project you have ever worked on synchronized, your notebook's disk
148 149 will fill up with old files. Each \fBfilesync\fR command will waste a lot of
149 150 time updating files you no longer care about.
150 151 .sp
151 152 .LP
152 153 If you delete the files from your notebook, \fBfilesync\fR will want to perform
153 154 the corresponding deletes on the server, which would not be what you wanted.
154 155 Rather, you would like a way to tell \fBfilesync\fR to stop synchronizing some
155 156 of the files. There are two ways to do this:
156 157 .RS +4
157 158 .TP
158 159 1.
159 160 Edit \fB$HOME/.packingrules\fR. Delete the rules for the files that you
160 161 want to delete.
161 162 .RE
162 163 .RS +4
163 164 .TP
164 165 2.
165 166 Delete \fB$HOME/.packingrules\fR. Use the \fBfilesync\fR command to specify
166 167 the files that you want synchronized.
167 168 .RE
168 169 .sp
169 170 .LP
170 171 Either way works, and you can choose the one that seems easiest to you. For
171 172 minor changes, it is probably easier to just edit \fB$HOME/.packingrules\fR.
172 173 For major changes it is probably easier to start from scratch.
173 174 .sp
174 175 .LP
175 176 Once \fBfilesync\fR is no longer synchronizing a set of files, you can delete
176 177 them from your notebook without having any effect on the server.
177 178 .SS "Nomadic Machines"
178 179 .sp
179 180 .LP
180 181 When using \fBfilesync\fR to keep files synchronized between nomadic machines
181 182 and a server, store the packing rules and baseline files on the nomadic
182 183 machines, not the server. If, when logged into your notebook, the \fBHOME\fR
183 184 environment variable does not normally point to a directory on your notebook,
184 185 you can use the \fBFILESYNC\fR environment variable to specify an alternate
185 186 location for the packing rules and baseline files.
186 187 .sp
187 188 .LP
188 189 Each nomadic machine should carry its own packing rules and baseline file.
189 190 Incorrect file synchronization can result if a server carries a baseline file
190 191 and multiple nomadic machines attempt to reconcile against the server's
191 192 baseline file. In this case, a nomadic machine could be using a baseline file
192 193 that does not accurately describe the state of its files. This might result in
193 194 incorrect reconciliations.
194 195 .sp
195 196 .LP
196 197 To safeguard against the dangers associated with a single baseline file being
197 198 shared by more than two machines, \fBfilesync\fR adds a default rule to each
198 199 new packing rules file. This default rule prevents the packing rules and
199 200 baseline files from being copied.
200 201 .SH OPTIONS
201 202 .sp
202 203 .LP
203 204 The following options are supported:
204 205 .sp
205 206 .ne 2
206 207 .na
207 208 \fB\fB-a\fR\fR
208 209 .ad
209 210 .RS 28n
210 211 Force the checking of Access Control Lists (\fBACL\fRs ) and attempt to make
211 212 them agree for all new and changed files. If it is not possible to set the
212 213 \fBACL\fR for a particular file, \fBfilesync\fR stops \fBACL\fR synchronization
213 214 for that file.
214 215 .sp
215 216 Some file systems do not support \fBACL\fRs . It is not possible to synchronize
216 217 \fBACL\fRs between file systems that support \fBACL\fRs and those that do not;
217 218 attempting to do so will result in numerous error messages.
218 219 .RE
219 220
220 221 .sp
221 222 .ne 2
222 223 .na
223 224 \fB\fB-d\fR\fI dest-dir\fR\fR
224 225 .ad
225 226 .RS 28n
226 227 Specify the directory on the destination system into which \fIfilename\fR is to
227 228 be copied. Use with the \fB-s\fR\fI source-dir\fR option and the \fIfilename\fR
228 229 operand. See \fB-s\fR and \fBOPERANDS\fR.
229 230 .RE
230 231
231 232 .sp
232 233 .ne 2
233 234 .na
234 235 \fB\fB-e\fR\fR
235 236 .ad
236 237 .RS 28n
237 238 Flag all differences. It may not be possible to resolve all conflicts involving
238 239 modes and ownership (unless \fBfilesync\fR is being run with root privileges).
239 240 If you cannot change the ownership or protections on a file, \fBfilesync\fR
240 241 will normally ignore conflicts in ownership and protection. If you specify the
241 242 \fB-e\fR (everything must agree) flag, however, \fBfilesync\fR will flag these
242 243 differences.
243 244 .RE
244 245
245 246 .sp
246 247 .ne 2
247 248 .na
248 249 \fB\fB\fR\fB-f\fR\fB src\fR | \fBdst\fR | \fBold\fR | \fBnew\fR\fR
249 250 .ad
250 251 .RS 28n
251 252 The \fB-f\fR option tells \fBfilesync\fR how to resolve conflicting changes. If
252 253 a file has been changed on both systems, and an \fB-f\fR option has been
253 254 specified, \fBfilesync\fR will retain the changes made on the favored system
254 255 and discard the changes made on the unfavored system.
255 256 .sp
256 257 Specify \fB-f\fR \fBsrc\fR to favor the source-system file. Specify \fB-f\fR
257 258 \fBdst\fR to favor the destination-system file. Specify \fB-f\fR \fBold\fR to
258 259 favor the older version of the file. Specify \fB-f\fR \fBnew\fR to favor the
259 260 newer version of the file.
260 261 .sp
261 262 It is possible to specify the \fB-f\fR and \fB-o\fR options in combination
262 263 if they both specify the same preference (\fBsrc \fRand\fB dst\fR). If
263 264 \fB-f\fR and \fB-o\fR conflict, the \fB-f\fR option is ignored. See the
264 265 \fB-o\fR option description.
265 266 .RE
266 267
267 268 .sp
268 269 .ne 2
269 270 .na
270 271 \fB\fB-h\fR\fR
271 272 .ad
272 273 .RS 28n
273 274 Halt on error. Normally, if \fBfilesync\fR encounters a read or write error
274 275 while copying files, it notes the error and the program continues, in an
275 276 attempt to reconcile other files. If the \fB-h\fR option is specified,
276 277 \fBfilesync\fR will immediately halt when one of these errors occurs and will
277 278 not try to process any more files.
278 279 .RE
279 280
280 281 .sp
281 282 .ne 2
282 283 .na
283 284 \fB\fB-m\fR\fR
284 285 .ad
285 286 .RS 28n
286 287 Ensure that both copies of the file have the same modification time. The
287 288 modification time for newly copied files is set to the time of reconciliation
288 289 by default. File changes are ordered by increasing modification times so that
289 290 the propagated files have the same relative modification time ordering as the
290 291 original changes. Users should be warned that there is usually some time skew
291 292 between any two systems, and transferring modification times from one system
292 293 to another can occasionally produce strange results.
293 294 .sp
294 295 There are instances in which using \fBfilesync\fR to update some (but not all)
295 296 files in a directory will confuse the \fBmake\fR program. If, for instance,
296 297 \fBfilesync\fR is keeping \fB\&.c\fR files synchronized, but ignoring
297 298 \fB\&.o\fR files, a changed \fB\&.c\fR file may show up with a modification
298 299 time prior to a \fB\&.o\fR file that was built from a prior version of the
299 300 \fB\&.c\fR file.
300 301 .RE
301 302
302 303 .sp
303 304 .ne 2
304 305 .na
305 306 \fB\fB-n\fR\fR
306 307 .ad
307 308 .RS 28n
308 309 Do not really make the changes. If the \fB-n\fR option is specified,
309 310 \fBfilesync\fR determines what changes have been made to files, and what
310 311 reconciliations are required and displays this information on the standard
311 312 output. No changes are made to files, including the packing rules file.
312 313 .sp
313 314 Specifying both the \fB-n\fR and \fB-o\fR options causes \fBfilesync\fR to
314 315 analyze the prevailing system and report the changes that have been made on
315 316 that system. Using \fB-n\fR and \fB-o\fR in combination is useful if your
316 317 machine is disconnected (and you cannot access the server) but you want to know
317 318 what changes have been made on the local machine. See the \fB-o\fR option
318 319 description.
319 320 .RE
320 321
321 322 .sp
322 323 .ne 2
323 324 .na
324 325 \fB\fB\fR\fB-o\fR\fB src | dst\fR\fR
325 326 .ad
326 327 .RS 28n
327 328 The \fB-o\fR option forces a one-way reconciliation, favoring either the source
328 329 system (\fBsrc\fR) or destination system (\fBdst\fR).
329 330 .sp
330 331 Specify \fB-o\fR \fBsrc\fR to propagate changes only from the source system to
331 332 the destination system. Changes made on the destination system are ignored.
332 333 \fBfilesync\fR aborts if it cannot access a source or destination directory.
333 334 .sp
334 335 Specify \fB-o\fR \fBdst\fR to propagate changes only from the destination
335 336 system to the source system. Changes made on the source system are ignored.
336 337 \fBfilesync\fR aborts if it cannot access a source or destination directory.
337 338 .sp
338 339 Specifying \fB-n\fR with the \fB-o\fR option causes \fBfilesync\fR to analyze
339 340 the prevailing system and reports on what changes have been made on that
340 341 system. Using \fB-n\fR and \fB-o\fR in combination is useful if a machine is
341 342 disconnected (and there is no access to the server), but you want to know what
342 343 changes have been made on the local machine. See the \fB-n\fR option
343 344 description.
344 345 .sp
345 346 It is possible to specify the \fB-o\fR and \fB-f\fR options in combination if
346 347 they both specify the same preference (\fBsrc\fR or \fBdst\fR). If \fB-o\fR and
347 348 \fB-f\fR options conflict, the \fB-f\fR option will be ignored. See the
348 349 \fB-f\fR option description.
349 350 .RE
350 351
351 352 .sp
352 353 .ne 2
353 354 .na
354 355 \fB\fB-q\fR\fR
355 356 .ad
356 357 .RS 28n
357 358 Suppress the standard \fBfilesync\fR messages that describe each reconciliation
358 359 action as it is performed.
359 360 .sp
360 361 The standard \fBfilesync\fR message describes each reconciliation action in the
361 362 form of a UNIX shell command (for example, \fBmv\fR, \fBln\fR, \fBcp\fR,
362 363 \fBrm\fR, \fBchmod\fR, \fBchown\fR, \fBchgrp\fR, \fBsetfacl\fR, and so forth).
363 364 .RE
364 365
365 366 .sp
366 367 .ne 2
367 368 .na
368 369 \fB\fB-r\fR\fI directory\fR\fR
369 370 .ad
370 371 .RS 28n
371 372 Limit the reconciliation to \fIdirectory\fR. Specify multiple directories with
372 373 multiple \fB-r\fR specifications.
373 374 .RE
374 375
375 376 .sp
376 377 .ne 2
377 378 .na
378 379 \fB\fB-s\fR\fI source-dir\fR\fR
379 380 .ad
380 381 .RS 28n
381 382 Specify the directory on the source system from which the \fIfilename\fR to be
382 383 copied is located. Use with the \fB-d\fR\fI dest-dir\fR option and the
383 384 \fIfilename\fR operand. See the \fB-d\fR option description and
384 385 \fBOPERANDS\fR.
385 386 .RE
386 387
387 388 .sp
388 389 .ne 2
389 390 .na
390 391 \fB\fB-v\fR\fR
391 392 .ad
392 393 .RS 28n
393 394 Display additional information about each file comparison as it is made on the
394 395 standard output.
395 396 .RE
396 397
397 398 .sp
398 399 .ne 2
399 400 .na
400 401 \fB\fB-y\fR\fR
401 402 .ad
402 403 .RS 28n
403 404 Bypass safety check prompts. Nomadic machines occasionally move between
404 405 domains, and many of the files on which \fBfilesync\fR operates are expected to
405 406 be accessed by NFS. There is a danger that someday \fBfilesync\fR will be
406 407 asked to reconcile local changes against the wrong file system or server. This
407 408 could result in a large number of inappropriate copies and deletions. To
408 409 prevent such a mishap, \fBfilesync\fR performs a few safety checks prior to
409 410 reconciliation. If large numbers of files are likely to be deleted, or if high
410 411 level directories have changed their I-node numbers, \fBfilesync\fR prompts
411 412 for a confirmation before reconciliation. If you know that this is likely, and
412 413 do not want to be prompted, use the \fB-y\fR (yes) option to automatically
413 414 confirm these prompts.
414 415 .RE
415 416
416 417 .SH OPERANDS
417 418 .sp
418 419 .LP
419 420 The following operands are supported:
420 421 .sp
421 422 .ne 2
422 423 .na
423 424 \fB\fIfilename\fR\fR
424 425 .ad
425 426 .RS 12n
426 427 The name of the ordinary file, directory, symbolic link, or special file in the
427 428 specified source directory (\fIsource-dir\fR) to be synchronized. Specify
428 429 multiple files by separating each filename by spaces. Use the \fIfilename\fR
429 430 operand with the \fB-s\fR and \fB-d\fR options. See \fBOPTIONS\fR.
430 431 .sp
431 432 If \fIfilename\fR is an ordinary file, that ordinary file will be replicated
432 433 (with the same \fIfilename\fR) in the specified destination directory
433 434 (\fIdest-dir\fR).
434 435 .sp
435 436 If \fIfilename\fR is a directory, that directory and all of the files and
436 437 subdirectories under it will be replicated (recursively) in the specified
437 438 destination directory (\fIdest-dir\fR).
438 439 .sp
439 440 If \fIfilename\fR is a symbolic link, a copy of that symbolic link will be
440 441 replicated in the specified destination directory (\fIdest-dir\fR).
441 442 .sp
442 443 If \fIfilename\fR is a special file, a special file with the same major or
443 444 minor device numbers will be replicated in the specified destination directory.
444 445 (\fIdest-dir).\fR Only super-users can use \fBfilesync\fR to create special
445 446 files.
446 447 .sp
447 448 Files created in the destination directory (\fIdest-dir\fR) will have the same
448 449 owner, group and other permissions as the files in the source directory.
449 450 .sp
450 451 If \fIfilename\fR contains escaped shell wildcard characters, the wildcard
451 452 characters are stored in \fB$HOME/.packingrules\fR and evaluated each time
452 453 \fBfilesync\fR is run.
453 454 .sp
454 455 For example, the following would make sure that the two specified files,
455 456 currently in \fB$RHOME\fR, were replicated in \fB$HOME\fR:
456 457 .sp
457 458 .in +2
458 459 .nf
459 460 \fBfilesync \fR\fB-s\fR\fB $RHOME \fR\fB-d\fR\fB $HOME a.c \|b.c\fR
460 461 .fi
461 462 .in -2
462 463 .sp
463 464
464 465 The following example would ensure that all of the \fB*.c\fR files in
465 466 \fB$RHOME\fR were replicated in \fB$HOME\fR, even if those files were not
466 467 created until later.
467 468 .sp
468 469 .in +2
469 470 .nf
470 471 \fBfilesync \fR\fB-s\fR\fB $RHOME \fR\fB-d\fR\fB $HOME '*.c'\fR
471 472 .fi
472 473 .in -2
473 474 .sp
474 475
475 476 If any of the destination files already exist, \fBfilesync\fR ensures that
476 477 they are identical and issues warnings if they are not.
477 478 .sp
478 479 Once files have been copied, the distinction between the source and destination
479 480 is a relatively arbitrary one (except for its use in the \fB-o\fR and \fB-f\fR
480 481 switches).
481 482 .RE
482 483
483 484 .SH ENVIRONMENT VARIABLES
484 485 .sp
485 486 .ne 2
486 487 .na
487 488 \fB\fBFILESYNC\fR\fR
488 489 .ad
489 490 .RS 15n
490 491 Specifies the default location of the \fBfilesync\fR packing rules and baseline
491 492 files. The default value for this variable is \fB$HOME\fR. The suffixes
492 493 \fB\&.packingrules\fR and \fB\&.filesync-base\fR will be appended to form the
493 494 names of the packing rules and baseline files.
494 495 .RE
495 496
496 497 .sp
497 498 .ne 2
498 499 .na
499 500 \fB\fBLC_MESSAGES\fR\fR
500 501 .ad
501 502 .RS 15n
502 503 Determines how diagnostic and informative messages are presented. In the "C"
503 504 locale, the messages are presented in the default form found in the program
504 505 itself (in most cases, U.S. English).
505 506 .RE
506 507
507 508 .SH EXIT STATUS
508 509 .sp
509 510 .LP
510 511 Normally, if all files are already up-to-date, or if all files were
511 512 successfully reconciled, \fBfilesync\fR will exit with a status of \fB0\fR.
512 513 However, if either the \fB-n\fR option was specified or any errors occurred,
513 514 the exit status will be the logical OR of the following:
514 515 .sp
515 516 .ne 2
516 517 .na
517 518 \fB\fB0\fR\fR
518 519 .ad
519 520 .RS 7n
520 521 No conflicts, all files up to date.
521 522 .RE
522 523
523 524 .sp
524 525 .ne 2
525 526 .na
526 527 \fB\fB1\fR\fR
527 528 .ad
528 529 .RS 7n
529 530 Some resolvable conflicts.
530 531 .RE
531 532
532 533 .sp
533 534 .ne 2
534 535 .na
535 536 \fB\fB2\fR\fR
536 537 .ad
537 538 .RS 7n
538 539 Some conflicts requiring manual resolution.
539 540 .RE
540 541
541 542 .sp
542 543 .ne 2
543 544 .na
544 545 \fB\fB4\fR\fR
545 546 .ad
546 547 .RS 7n
547 548 Some specified files did not exist.
548 549 .RE
549 550
550 551 .sp
551 552 .ne 2
552 553 .na
553 554 \fB\fB8\fR\fR
554 555 .ad
555 556 .RS 7n
556 557 Insufficient permission for some files.
557 558 .RE
558 559
559 560 .sp
560 561 .ne 2
561 562 .na
562 563 \fB\fB16\fR\fR
563 564 .ad
564 565 .RS 7n
565 566 Errors accessing packing rules or baseline file.
566 567 .RE
567 568
568 569 .sp
569 570 .ne 2
570 571 .na
571 572 \fB\fB32\fR\fR
572 573 .ad
573 574 .RS 7n
574 575 Invalid arguments.
575 576 .RE
576 577
577 578 .sp
578 579 .ne 2
579 580 .na
580 581 \fB\fB64\fR\fR
581 582 .ad
582 583 .RS 7n
583 584 Unable to access either or both of the specified \fBsrc\fR or \fBdst\fR
584 585 directories.
585 586 .RE
586 587
587 588 .sp
588 589 .ne 2
589 590 .na
590 591 \fB\fB128\fR\fR
591 592 .ad
592 593 .RS 7n
593 594 Miscellaneous other failures.
594 595 .RE
595 596
596 597 .SH FILES
597 598 .sp
598 599 .ne 2
599 600 .na
600 601 \fB\fB$HOME/.packingrules\fR\fR
601 602 .ad
602 603 .RS 24n
603 604 list of files to be kept synchronized
604 605 .RE
605 606
606 607 .sp
607 608 .ne 2
|
↓ open down ↓ |
553 lines elided |
↑ open up ↑ |
608 609 .na
609 610 \fB\fB$HOME/.filesync-base\fR\fR
610 611 .ad
611 612 .RS 24n
612 613 baseline summary file
613 614 .RE
614 615
615 616 .SH SEE ALSO
616 617 .sp
617 618 .LP
618 -\fBcachefspack\fR(1M), \fBpackingrules\fR(4), \fBattributes\fR(5)
619 +\fBpackingrules\fR(4), \fBattributes\fR(5)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX