Print this page
6198 Let's EOL cachefs
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man4/packingrules.4.man.txt
+++ new/usr/src/man/man4/packingrules.4.man.txt
1 1 PACKINGRULES(4) File Formats PACKINGRULES(4)
2 2
3 3
4 4
5 5 NAME
6 - packingrules - packing rules file for cachefs and filesync
6 + packingrules - packing rules file for filesync
7 7
8 8 SYNOPSIS
9 9 $HOME/.packingrules
10 10
11 11
12 12 DESCRIPTION
13 - $HOME/.packingrules is a packing rules file for filesync and
14 - cachefspack. $HOME/.packingrules contains a list of directories and
15 - files that are to be packed and synchronized. It also contains a list
16 - of directories and files that are to be specifically excluded from
17 - packing and synchronization. See filesync(1) and cachefspack(1M).
13 + $HOME/.packingrules is a packing rules file for filesync.
14 + $HOME/.packingrules contains a list of directories and files that are
15 + to be packed and synchronized. It also contains a list of directories
16 + and files that are to be specifically excluded from packing and
17 + synchronization. See filesync(1).
18 18
19 19
20 20 The $HOME/.packingrules file is automatically created if users invoke
21 21 filesync with filename arguments. By using filesync options, users can
22 22 augment the packing rules in $HOME/.packingrules.
23 23
24 24
25 25 Many users choose to manually create the packing rules file and edit it
26 26 by hand. Users can edit $HOME/.packingrules (using any editor) to
27 27 permanently change the $HOME/.packingrules file, or to gain access to
28 28 more powerful options that are not available from the command line
29 29 (such as IGNORE commands). It is much easier to enter complex wildcard
30 30 expressions by editing the $HOME/.packingrules file.
31 31
32 32
33 33 Blank lines and lines that begin with a pound sign (`#') are ignored.
34 34
35 35
36 36 Any line can be continued by placing a backslash (`\') immediately
37 37 before the NEWLINE.
38 38
39 39
40 40 All other lines in the $HOME/.packingrules file have one of the
41 41 following formats:
42 42
43 43 PACKINGRULES
44 44 major. minor. This line is not actually required, but it should be
45 45 the first line of every packing rules file. This line identifies
46 46 the packing rules file for the file(1) command and specifies a
47 47 format version number. The current version number is 1.1. See
48 48 file(1).
49 49
50 50
51 51 BASE directory-1 [directory-2]
52 52 This line identifies a directory (or pair of directories) under
53 53 which files should be packed and synchronized. At least one
54 54 directory name must be specified. For rules that are to be used by
55 55 filesync a second directory name (where the copies are to be kept)
56 56 must also be specified. The arguments must be fully qualified path
57 57 names, and may include environment variables.
58 58
59 59
60 60 LIST name ...
61 61 This line enumerates a list of files and sub-directories (beneath
62 62 the current BASE) that are to be kept synchronized. This
63 63 specification is recursive, in that specifying the name of a
64 64 directory automatically includes all files and subdirectories it
65 65 contains. Regular expressions (as described in glob and gmatch)
66 66 are permitted. See glob(1) and gmatch(3GEN).
67 67
68 68
69 69 IGNORE name ...
70 70 This line enumerates a list of files that are not to be kept
71 71 synchronized. Regular expressions (using glob and gmatch) are
72 72 permitted.
73 73
74 74
75 75
76 76 There are important differences between the arguments to LIST and
77 77 IGNORE statements. The arguments to a LIST statement can contain
78 78 slashes and are interpreted as file names relative to the BASE
79 79 directories. The arguments to an IGNORE statement are simpler names or
80 80 expressions that cannot contain slashes. An IGNORE statement will not
81 81 override a LIST statement. IGNORE statements only exclude files that
82 82 are found beneath LISTed directories.
83 83
84 84
85 85 If the first name argument to a LIST statement begins with an
86 86 exclamation point (`!'), the remainder of the statement will be
87 87 executed as a command. The command will be run in the current BASE
88 88 directory. The output of the command will be treated as a list of
89 89 newline separated file names to be packed/synchronized. The resulting
90 90 file names will be interpreted relative to the enclosing BASE
91 91 directory.
92 92
93 93
94 94 If the first name argument to an IGNORE statement begins with an
95 95 exclamation point (`!'), the remainder of the statement will be
96 96 executed as a command. The command will be run in the current BASE
97 97 directory. The command will be expected to figure out which names
98 98 should not be synchronized. The output of the command will be treated
99 99 as a list of newline separated file names that should be excluded from
100 100 the packing and synchronization list.
101 101
102 102
103 103 Commands will be broken into distinct arguments and run directly with
104 104 sh -c. Blanks can be embedded in an argument by escaping them with a
105 105 backslash (`\') or enclosing the argument in double quotes (` " ').
106 106 Double quotes can be passed in arguments by escaping the double quotes
107 107 with a backslash (`\').
108 108
109 109
110 110 LIST lines only apply to the BASE statement that precedes them.
111 111 IGNORE lines can appear before any BASE statement (in which case they
112 112 apply to all BASEs) or after a BASE statement (in which case they only
113 113 apply to the BASE that precedes them). Any number of these statements
114 114 can occur in any combination. The order is not important.
115 115
116 116 EXAMPLES
117 117 Example 1 A sample $HOME.packingrules file.
118 118
119 119
120 120 The use of these statements is illustrated in the following
121 121 $HOME.packingrules file.
122 122
123 123
124 124 #
125 125 # junk files, not worth copying
126 126 #
127 127 IGNORE core *.o *.bak *%
128 128 #
129 129 # most of the stuff I want to keep in sync is in my $HOME
130 130 #
131 131 BASE /net/bigserver/export/home/myname $HOME
132 132 # everything in my work sub-directory should be maintained
133 133 LIST work
134 134 # a few of my favorite mail boxes should be replicated
135 135 LIST m/incoming
136 136 LIST m/action
137 137 LIST m/pending
138 138 #
139 139 # I like to carry around a couple of project directories
140 140 # but skip all the postscript output
141 141 #
142 142 BASE /net/bigserver/export/projects $HOME/projects
143 143 LIST poindexter epiphany
144 144 IGNORE *.ps
145 145 #
146 146 # the foonly package should always be kept on every machine
147 147 #
148 148 BASE /net/bigserver/opt/foonly /opt/foonly
|
↓ open down ↓ |
121 lines elided |
↑ open up ↑ |
149 149 LIST !cat .packinglist
150 150 #
151 151 # and the latest executables for the standard build environment
152 152 #
153 153 BASE /net/bigserver/export/buildenv $HOME/buildenv
154 154 LIST !find . -type f -a -perm -111 -a -print
155 155
156 156
157 157
158 158 SEE ALSO
159 - file(1), filesync(1), cachefspack(1M)
159 + file(1), filesync(1)
160 160
161 161
162 162
163 - December 23, 1996 PACKINGRULES(4)
163 + September 8, 2015 PACKINGRULES(4)
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX