Cross Reference: /opensolaris-onvv-gate/usr/src/cmd/filesync/README

5 # Common Development and Distribution License, Version 1.0 only
12 # and limitations under the License.
15 # file and include the License file at usr/src/OPENSOLARIS.LICENSE.
36 		data structures		major structures and their contents
40 	Modules				list and descriptions of files
54 	changed, and to propagate the changes in order to bring the
59 	The files and directory trees to be compared are determined
61 	format (packingrules.4) permits files and or trees to be
64 	and for running programs to generate lists of files and
70 	ownership and protections.  For files that are already
71 	in the baseline snapshot, if the sizes and modification
79 	the file is flagged and the user is asked to reconcile the
90 		and on the source and destination sides.
108 			files and or directories to be included
117 		the files that we are supposed to keep in sync, and
121 		three hiearchies (baseline, source and destination).
124 		size, owner, protection, mod time) and keep separate
146 			sibling and child pointers to give them tree structure
148 			"fileinfo" information from the src, dest, and baseline
152 			reconciliation and record what happened to it.
159 			ownership, protection, and acls
165 		are believed to descibe files that have changed and require
167 		and to preserve relative modification times.
176 		find out what files exist and stating all of
181 		limiting our attention to specific files and trees).
186 		all restrictions and ignores take effect during this pass.
190 		given the baseline and all of the current stat information
192 		have changed and queue it for pass III.  This pass doesn't
198 		which the files will be processed in pass III, and the
204 		actually changed and which versions deserve to win.  If
211 		defines for limits, sizes and return codes
225 		definitions and declarations for routines for error
226 		simulation and bit-map display.
229 		routines to get, set, compare, and display Access Control Lists
235 		routines to examine the in-core list of files and
236 		determine what has changed (and therefore what is
241 		routines to read and write the baseline file
242 		routines to search and manipulate the in-core base list
244 		data structures and routines, used to sumulate errors
245 		and produce debug output, that map between bits (as found
255 		wild cards and embedded environment variables.
258 		files to be ignored, and to check file names against
262 		parameter validation, error reporting, and the
266 		have changed, and figure out what the appropriate
272 		routines to read and write the rules file
273 		routines to add rules and enumerate in-core rules
285 		read the above notes on data structures and then
294 			and it is unquestionably the most important
299 		in eval.c: read evaluate, eval_file, walker, and note_info
310 		in simple ways, and can (for the most part) be understood
323 		program, and while they are broken into specialized
327 			main.c		setup and control
331 			action.c	execution and book-keeping
387 	found).  Others are more subtle and control the evaluation
398 				and should not be recursively walked.
400 		F_EVALUATE	this node was found in evaluation and
409 				(and anything below it)
420 			listed files and directories should be evaluated
421 			and analyzed.  sparse directories should not be