Commit | Line | Data |
---|---|---|
9e3c856a | 1 | mailto(rsync-bugs@samba.org) |
db8f3f73 | 2 | manpage(rsyncd.conf)(5)(29 Jun 2008)()() |
d90338ce | 3 | manpagename(rsyncd.conf)(configuration file for rsync in daemon mode) |
41059f75 AT |
4 | manpagesynopsis() |
5 | ||
6 | rsyncd.conf | |
7 | ||
8 | manpagedescription() | |
9 | ||
10 | The rsyncd.conf file is the runtime configuration file for rsync when | |
f97c2d4a | 11 | run as an rsync daemon. |
41059f75 AT |
12 | |
13 | The rsyncd.conf file controls authentication, access, logging and | |
14 | available modules. | |
15 | ||
16 | manpagesection(FILE FORMAT) | |
17 | ||
f97c2d4a | 18 | The file consists of modules and parameters. A module begins with the |
41059f75 | 19 | name of the module in square brackets and continues until the next |
0abe148f | 20 | module begins. Modules contain parameters of the form "name = value". |
41059f75 | 21 | |
faa82484 | 22 | The file is line-based -- that is, each newline-terminated line represents |
41059f75 AT |
23 | either a comment, a module name or a parameter. |
24 | ||
f97c2d4a | 25 | Only the first equals sign in a parameter is significant. Whitespace before |
41059f75 AT |
26 | or after the first equals sign is discarded. Leading, trailing and internal |
27 | whitespace in module and parameter names is irrelevant. Leading and | |
28 | trailing whitespace in a parameter value is discarded. Internal whitespace | |
29 | within a parameter value is retained verbatim. | |
30 | ||
f97c2d4a | 31 | Any line beginning with a hash (#) is ignored, as are lines containing |
41059f75 AT |
32 | only whitespace. |
33 | ||
e22de162 | 34 | Any line ending in a \ is "continued" on the next line in the |
41059f75 AT |
35 | customary UNIX fashion. |
36 | ||
37 | The values following the equals sign in parameters are all either a string | |
38 | (no quotes needed) or a boolean, which may be given as yes/no, 0/1 or | |
39 | true/false. Case is not significant in boolean values, but is preserved | |
f97c2d4a | 40 | in string values. |
41059f75 | 41 | |
5315b793 | 42 | manpagesection(LAUNCHING THE RSYNC DAEMON) |
41059f75 | 43 | |
faa82484 | 44 | The rsync daemon is launched by specifying the bf(--daemon) option to |
f97c2d4a | 45 | rsync. |
f5c20813 MP |
46 | |
47 | The daemon must run with root privileges if you wish to use chroot, to | |
48 | bind to a port numbered under 1024 (as is the default 873), or to set | |
49 | file ownership. Otherwise, it must just have permission to read and | |
50 | write the appropriate data, log, and lock files. | |
41059f75 | 51 | |
04657e42 DD |
52 | You can launch it either via inetd, as a stand-alone daemon, or from |
53 | an rsync client via a remote shell. If run as a stand-alone daemon then | |
faa82484 | 54 | just run the command "bf(rsync --daemon)" from a suitable startup script. |
41059f75 AT |
55 | |
56 | When run via inetd you should add a line like this to /etc/services: | |
57 | ||
faa82484 | 58 | verb( rsync 873/tcp) |
41059f75 | 59 | |
e22de162 | 60 | and a single line something like this to /etc/inetd.conf: |
f97c2d4a | 61 | |
faa82484 | 62 | verb( rsync stream tcp nowait root /usr/bin/rsync rsyncd --daemon) |
41059f75 | 63 | |
79f118d8 DD |
64 | Replace "/usr/bin/rsync" with the path to where you have rsync installed on |
65 | your system. You will then need to send inetd a HUP signal to tell it to | |
66 | reread its config file. | |
41059f75 | 67 | |
d90338ce | 68 | Note that you should bf(not) send the rsync daemon a HUP signal to force |
30e8c8e1 | 69 | it to reread the tt(rsyncd.conf) file. The file is re-read on each client |
f97c2d4a | 70 | connection. |
41059f75 | 71 | |
1b8e0e87 | 72 | manpagesection(GLOBAL PARAMETERS) |
41059f75 AT |
73 | |
74 | The first parameters in the file (before a [module] header) are the | |
f97c2d4a | 75 | global parameters. |
41059f75 AT |
76 | |
77 | You may also include any module parameters in the global part of the | |
78 | config file in which case the supplied value will override the | |
79 | default for that parameter. | |
80 | ||
81 | startdit() | |
1b8e0e87 | 82 | dit(bf(motd file)) This parameter allows you to specify a |
5315b793 | 83 | "message of the day" to display to clients on each connect. This |
41059f75 AT |
84 | usually contains site information and any legal notices. The default |
85 | is no motd file. | |
2206abf8 WD |
86 | This can be overridden by the bf(--dparam=motdfile=FILE) |
87 | command-line option when starting the daemon. | |
41059f75 | 88 | |
1b8e0e87 | 89 | dit(bf(pid file)) This parameter tells the rsync daemon to write |
306847ea WD |
90 | its process ID to that file. If the file already exists, the rsync |
91 | daemon will abort rather than overwrite the file. | |
2206abf8 WD |
92 | This can be overridden by the bf(--dparam=pidfile=FILE) |
93 | command-line option when starting the daemon. | |
37863201 | 94 | |
f7112154 WD |
95 | dit(bf(port)) You can override the default port the daemon will listen on |
96 | by specifying this value (defaults to 873). This is ignored if the daemon | |
97 | is being run by inetd, and is superseded by the bf(--port) command-line option. | |
98 | ||
99 | dit(bf(address)) You can override the default IP address the daemon | |
100 | will listen on by specifying this value. This is ignored if the daemon is | |
101 | being run by inetd, and is superseded by the bf(--address) command-line option. | |
102 | ||
1b8e0e87 | 103 | dit(bf(socket options)) This parameter can provide endless fun for people |
a6801c39 AT |
104 | who like to tune their systems to the utmost degree. You can set all |
105 | sorts of socket options which may make transfers faster (or | |
19826af5 | 106 | slower!). Read the man page for the code(setsockopt()) system call for |
a6801c39 | 107 | details on some of the options you may be able to set. By default no |
2206abf8 WD |
108 | special socket options are set. These settings can also be specified |
109 | via the bf(--sockopts) command-line option. | |
a6801c39 | 110 | |
41059f75 AT |
111 | enddit() |
112 | ||
1b8e0e87 | 113 | manpagesection(MODULE PARAMETERS) |
41059f75 | 114 | |
1b8e0e87 | 115 | After the global parameters you should define a number of modules, each |
41059f75 AT |
116 | module exports a directory tree as a symbolic name. Modules are |
117 | exported by specifying a module name in square brackets [module] | |
1b8e0e87 | 118 | followed by the parameters for that module. |
ec8637f3 WD |
119 | The module name cannot contain a slash or a closing square bracket. If the |
120 | name contains whitespace, each internal sequence of whitespace will be | |
121 | changed into a single space, while leading or trailing whitespace will be | |
122 | discarded. | |
41059f75 AT |
123 | |
124 | startdit() | |
125 | ||
1b8e0e87 | 126 | dit(bf(comment)) This parameter specifies a description string |
41059f75 AT |
127 | that is displayed next to the module name when clients obtain a list |
128 | of available modules. The default is no comment. | |
129 | ||
1b8e0e87 WD |
130 | dit(bf(path)) This parameter specifies the directory in the daemon's |
131 | filesystem to make available in this module. You must specify this parameter | |
30e8c8e1 | 132 | for each module in tt(rsyncd.conf). |
8638dd48 | 133 | |
d90338ce | 134 | dit(bf(use chroot)) If "use chroot" is true, the rsync daemon will chroot |
8638dd48 DD |
135 | to the "path" before starting the file transfer with the client. This has |
136 | the advantage of extra protection against possible implementation security | |
f97c2d4a | 137 | holes, but it has the disadvantages of requiring super-user privileges, |
1a7f3d99 | 138 | of not being able to follow symbolic links that are either absolute or outside |
0b52f94d WD |
139 | of the new root path, and of complicating the preservation of users and groups |
140 | by name (see below). | |
2fe1feea WD |
141 | |
142 | As an additional safety feature, you can specify a dot-dir in the module's | |
143 | "path" to indicate the point where the chroot should occur. This allows rsync | |
144 | to run in a chroot with a non-"/" path for the top of the transfer hierarchy. | |
145 | Doing this guards against unintended library loading (since those absolute | |
146 | paths will not be inside the transfer hierarchy unless you have used an unwise | |
147 | pathname), and lets you setup libraries for the chroot that are outside of the | |
148 | transfer. For example, specifying "/var/rsync/./module1" will chroot to the | |
149 | "/var/rsync" directory and set the inside-chroot path to "/module1". If you | |
150 | had omitted the dot-dir, the chroot would have used the whole path, and the | |
151 | inside-chroot path would have been "/". | |
152 | ||
153 | When "use chroot" is false or the inside-chroot path is not "/", rsync will: | |
154 | (1) munge symlinks by | |
9585b276 WD |
155 | default for security reasons (see "munge symlinks" for a way to turn this |
156 | off, but only if you trust your users), (2) substitute leading slashes in | |
157 | absolute paths with the module's path (so that options such as | |
158 | bf(--backup-dir), bf(--compare-dest), etc. interpret an absolute path as | |
159 | rooted in the module's "path" dir), and (3) trim ".." path elements from | |
2fe1feea | 160 | args if rsync believes they would escape the module hierarchy. |
9585b276 WD |
161 | The default for "use chroot" is true, and is the safer choice (especially |
162 | if the module is not read-only). | |
41059f75 | 163 | |
1b8e0e87 | 164 | When this parameter is enabled, rsync will not attempt to map users and groups |
0b52f94d WD |
165 | by name (by default), but instead copy IDs as though bf(--numeric-ids) had |
166 | been specified. In order to enable name-mapping, rsync needs to be able to | |
d99b4ccf | 167 | use the standard library functions for looking up names and IDs (i.e. |
0b52f94d WD |
168 | code(getpwuid()), code(getgrgid()), code(getpwname()), and code(getgrnam())). |
169 | This means the rsync | |
170 | process in the chroot hierarchy will need to have access to the resources | |
d99b4ccf | 171 | used by these library functions (traditionally /etc/passwd and |
0b52f94d WD |
172 | /etc/group, but perhaps additional dynamic libraries as well). |
173 | ||
174 | If you copy the necessary resources into the module's chroot area, you | |
175 | should protect them through your OS's normal user/group or ACL settings (to | |
176 | prevent the rsync module's user from being able to change them), and then | |
177 | hide them from the user's view via "exclude" (see how in the discussion of | |
1b8e0e87 WD |
178 | that parameter). At that point it will be safe to enable the mapping of users |
179 | and groups by name using the "numeric ids" daemon parameter (see below). | |
0b52f94d WD |
180 | |
181 | Note also that you are free to setup custom user/group information in the | |
182 | chroot area that is different from your normal system. For example, you | |
183 | could abbreviate the list of users and groups. | |
184 | ||
1b8e0e87 | 185 | dit(bf(numeric ids)) Enabling this parameter disables the mapping |
0b52f94d WD |
186 | of users and groups by name for the current daemon module. This prevents |
187 | the daemon from trying to load any user/group-related files or libraries. | |
1b8e0e87 | 188 | This enabling makes the transfer behave as if the client had passed |
0b52f94d WD |
189 | the bf(--numeric-ids) command-line option. By default, this parameter is |
190 | enabled for chroot modules and disabled for non-chroot modules. | |
191 | ||
1b8e0e87 | 192 | A chroot-enabled module should not have this parameter enabled unless you've |
0b52f94d WD |
193 | taken steps to ensure that the module has the necessary resources it needs |
194 | to translate names, and that it is not possible for a user to change those | |
195 | resources. | |
cb290916 | 196 | |
1b8e0e87 | 197 | dit(bf(munge symlinks)) This parameter tells rsync to modify |
9585b276 WD |
198 | all incoming symlinks in a way that makes them unusable but recoverable |
199 | (see below). This should help protect your files from user trickery when | |
200 | your daemon module is writable. The default is disabled when "use chroot" | |
2fe1feea | 201 | is on and the inside-chroot path is "/", otherwise it is enabled. |
9585b276 | 202 | |
1b8e0e87 | 203 | If you disable this parameter on a daemon that is not read-only, there |
9585b276 WD |
204 | are tricks that a user can play with uploaded symlinks to access |
205 | daemon-excluded items (if your module has any), and, if "use chroot" | |
206 | is off, rsync can even be tricked into showing or changing data that | |
207 | is outside the module's path (as access-permissions allow). | |
208 | ||
209 | The way rsync disables the use of symlinks is to prefix each one with | |
210 | the string "/rsyncd-munged/". This prevents the links from being used | |
1b8e0e87 | 211 | as long as that directory does not exist. When this parameter is enabled, |
9585b276 | 212 | rsync will refuse to run if that path is a directory or a symlink to |
1b8e0e87 | 213 | a directory. When using the "munge symlinks" parameter in a chroot area |
2fe1feea WD |
214 | that has an inside-chroot path of "/", you should add "/rsyncd-munged/" |
215 | to the exclude setting for the module so that | |
5288be3a | 216 | a user can't try to create it. |
9585b276 WD |
217 | |
218 | Note: rsync makes no attempt to verify that any pre-existing symlinks in | |
219 | the hierarchy are as safe as you want them to be. If you setup an rsync | |
220 | daemon on a new area or locally add symlinks, you can manually protect your | |
221 | symlinks from being abused by prefixing "/rsyncd-munged/" to the start of | |
222 | every symlink's value. There is a perl script in the support directory | |
223 | of the source code named "munge-symlinks" that can be used to add or remove | |
224 | this prefix from your symlinks. | |
225 | ||
1b8e0e87 | 226 | When this parameter is disabled on a writable module and "use chroot" is off |
2fe1feea | 227 | (or the inside-chroot path is not "/"), |
ef3f14e6 WD |
228 | incoming symlinks will be modified to drop a leading slash and to remove ".." |
229 | path elements that rsync believes will allow a symlink to escape the module's | |
230 | hierarchy. There are tricky ways to work around this, though, so you had | |
1b8e0e87 | 231 | better trust your users if you choose this combination of parameters. |
ef3f14e6 | 232 | |
0b52f94d WD |
233 | dit(bf(charset)) This specifies the name of the character set in which the |
234 | module's filenames are stored. If the client uses an bf(--iconv) option, | |
235 | the daemon will use the value of the "charset" parameter regardless of the | |
236 | character set the client actually passed. This allows the daemon to | |
237 | support charset conversion in a chroot module without extra files in the | |
238 | chroot area, and also ensures that name-translation is done in a consistent | |
239 | manner. If the "charset" parameter is not set, the bf(--iconv) option is | |
240 | refused, just as if "iconv" had been specified via "refuse options". | |
241 | ||
242 | If you wish to force users to always use bf(--iconv) for a particular | |
243 | module, add "no-iconv" to the "refuse options" parameter. Keep in mind | |
244 | that this will restrict access to your module to very new rsync clients. | |
245 | ||
1b8e0e87 | 246 | dit(bf(max connections)) This parameter allows you to |
9ef1cc7c DD |
247 | specify the maximum number of simultaneous connections you will allow. |
248 | Any clients connecting when the maximum has been reached will receive a | |
3170b209 WD |
249 | message telling them to try later. The default is 0, which means no limit. |
250 | A negative value disables the module. | |
1b8e0e87 | 251 | See also the "lock file" parameter. |
5e71c444 | 252 | |
1b8e0e87 | 253 | dit(bf(log file)) When the "log file" parameter is set to a non-empty |
ccd2966d WD |
254 | string, the rsync daemon will log messages to the indicated file rather |
255 | than using syslog. This is particularly useful on systems (such as AIX) | |
256 | where code(syslog()) doesn't work for chrooted programs. The file is | |
257 | opened before code(chroot()) is called, allowing it to be placed outside | |
258 | the transfer. If this value is set on a per-module basis instead of | |
259 | globally, the global log will still contain any authorization failures | |
260 | or config-file error messages. | |
261 | ||
2206abf8 | 262 | If the daemon fails to open the specified file, it will fall back to |
ccd2966d WD |
263 | using syslog and output an error about the failure. (Note that the |
264 | failure to open the specified log file used to be a fatal error.) | |
265 | ||
2206abf8 WD |
266 | This setting can be overridden by using the bf(--log-file=FILE) or |
267 | bf(--dparam=logfile=FILE) command-line options. The former overrides | |
268 | all the log-file parameters of the daemon and all module settings. | |
269 | The latter sets the daemon's log file and the default for all the | |
270 | modules, which still allows modules to override the default setting. | |
271 | ||
1b8e0e87 | 272 | dit(bf(syslog facility)) This parameter allows you to |
ccd2966d WD |
273 | specify the syslog facility name to use when logging messages from the |
274 | rsync daemon. You may use any standard syslog facility name which is | |
275 | defined on your system. Common names are auth, authpriv, cron, daemon, | |
276 | ftp, kern, lpr, mail, news, security, syslog, user, uucp, local0, | |
277 | local1, local2, local3, local4, local5, local6 and local7. The default | |
278 | is daemon. This setting has no effect if the "log file" setting is a | |
279 | non-empty string (either set in the per-modules settings, or inherited | |
280 | from the global settings). | |
281 | ||
1b8e0e87 | 282 | dit(bf(max verbosity)) This parameter allows you to control |
21611119 WD |
283 | the maximum amount of verbose information that you'll allow the daemon to |
284 | generate (since the information goes into the log file). The default is 1, | |
285 | which allows the client to request one level of verbosity. | |
286 | ||
1b8e0e87 WD |
287 | dit(bf(lock file)) This parameter specifies the file to use to |
288 | support the "max connections" parameter. The rsync daemon uses record | |
5e71c444 | 289 | locking on this file to ensure that the max connections limit is not |
f97c2d4a | 290 | exceeded for the modules sharing the lock file. |
9ef1cc7c | 291 | The default is tt(/var/run/rsyncd.lock). |
5e71c444 | 292 | |
1b8e0e87 | 293 | dit(bf(read only)) This parameter determines whether clients |
41059f75 AT |
294 | will be able to upload files or not. If "read only" is true then any |
295 | attempted uploads will fail. If "read only" is false then uploads will | |
d90338ce | 296 | be possible if file permissions on the daemon side allow them. The default |
41059f75 AT |
297 | is for all modules to be read only. |
298 | ||
1b8e0e87 | 299 | dit(bf(write only)) This parameter determines whether clients |
7a92ded3 WD |
300 | will be able to download files or not. If "write only" is true then any |
301 | attempted downloads will fail. If "write only" is false then downloads | |
d90338ce | 302 | will be possible if file permissions on the daemon side allow them. The |
1b8e0e87 | 303 | default is for this parameter to be disabled. |
7a92ded3 | 304 | |
1b8e0e87 | 305 | dit(bf(list)) This parameter determines if this module should be |
41059f75 AT |
306 | listed when the client asks for a listing of available modules. By |
307 | setting this to false you can create hidden modules. The default is | |
308 | for modules to be listable. | |
309 | ||
1b8e0e87 | 310 | dit(bf(uid)) This parameter specifies the user name or user ID that |
716baed7 | 311 | file transfers to and from that module should take place as when the daemon |
1b8e0e87 | 312 | was run as root. In combination with the "gid" parameter this determines what |
2af27ad9 MP |
313 | file permissions are available. The default is uid -2, which is normally |
314 | the user "nobody". | |
41059f75 | 315 | |
1b8e0e87 | 316 | dit(bf(gid)) This parameter specifies the group name or group ID that |
716baed7 | 317 | file transfers to and from that module should take place as when the daemon |
1b8e0e87 | 318 | was run as root. This complements the "uid" parameter. The default is gid -2, |
2af27ad9 | 319 | which is normally the group "nobody". |
41059f75 | 320 | |
9439c0cb WD |
321 | dit(bf(fake super)) Setting "fake super = yes" for a module causes the |
322 | daemon side to behave as if the bf(--fake-user) command-line option had | |
323 | been specified. This allows the full attributes of a file to be stored | |
324 | without having to have the daemon actually running as root. | |
325 | ||
f28bf7f4 WD |
326 | dit(bf(filter)) The daemon has its own filter chain that determines what files |
327 | it will let the client access. This chain is not sent to the client and is | |
328 | independent of any filters the client may have specified. Files excluded by | |
329 | the daemon filter chain (bf(daemon-excluded) files) are treated as non-existent | |
330 | if the client tries to pull them, are skipped with an error message if the | |
331 | client tries to push them (triggering exit code 23), and are never deleted from | |
332 | the module. You can use daemon filters to prevent clients from downloading or | |
333 | tampering with private administrative files, such as files you may add to | |
100200d0 | 334 | support uid/gid name translations. |
f28bf7f4 WD |
335 | |
336 | The daemon filter chain is built from the "filter", "include from", "include", | |
337 | "exclude from", and "exclude" parameters, in that order of priority. Anchored | |
338 | patterns are anchored at the root of the module. To prevent access to an | |
339 | entire subtree, for example, "/secret", you em(must) exclude everything in the | |
340 | subtree; the easiest way to do this is with a triple-star pattern like | |
341 | "/secret/***". | |
342 | ||
343 | The "filter" parameter takes a space-separated list of daemon filter rules, | |
344 | though it is smart enough to know not to split a token at an internal space in | |
345 | a rule (e.g. "- /foo - /bar" is parsed as two rules). You may specify one or | |
100200d0 MM |
346 | more merge-file rules using the normal syntax. Only one "filter" parameter can |
347 | apply to a given module in the config file, so put all the rules you want in a | |
348 | single parameter. Note that per-directory merge-file rules do not provide as | |
349 | much protection as global rules, but they can be used to make bf(--delete) work | |
350 | better during a client download operation if the per-dir merge files are | |
351 | included in the transfer and the client requests that they be used. | |
f28bf7f4 | 352 | |
1b8e0e87 | 353 | dit(bf(exclude)) This parameter takes a space-separated list of daemon |
f28bf7f4 WD |
354 | exclude patterns. As with the client bf(--exclude) option, patterns can be |
355 | qualified with "- " or "+ " to explicitly indicate exclude/include. Only one | |
356 | "exclude" parameter can apply to a given module. See the "filter" parameter | |
357 | for a description of how excluded files affect the daemon. | |
358 | ||
359 | dit(bf(include)) Use an "include" to override the effects of the "exclude" | |
360 | parameter. Only one "include" parameter can apply to a given module. See the | |
361 | "filter" parameter for a description of how excluded files affect the daemon. | |
362 | ||
1b8e0e87 | 363 | dit(bf(exclude from)) This parameter specifies the name of a file |
f28bf7f4 WD |
364 | on the daemon that contains daemon exclude patterns, one per line. Only one |
365 | "exclude from" parameter can apply to a given module; if you have multiple | |
366 | exclude-from files, you can specify them as a merge file in the "filter" | |
367 | parameter. See the "filter" parameter for a description of how excluded files | |
368 | affect the daemon. | |
369 | ||
370 | dit(bf(include from)) Analogue of "exclude from" for a file of daemon include | |
371 | patterns. Only one "include from" parameter can apply to a given module. See | |
372 | the "filter" parameter for a description of how excluded files affect the | |
373 | daemon. | |
cd64343a | 374 | |
1b8e0e87 | 375 | dit(bf(incoming chmod)) This parameter allows you to specify a set of |
c094d932 WD |
376 | comma-separated chmod strings that will affect the permissions of all |
377 | incoming files (files that are being received by the daemon). These | |
44a8e86d WD |
378 | changes happen after all other permission calculations, and this will |
379 | even override destination-default and/or existing permissions when the | |
380 | client does not specify bf(--perms). | |
fa3e4a05 WD |
381 | See the description of the bf(--chmod) rsync option and the bf(chmod)(1) |
382 | manpage for information on the format of this string. | |
c094d932 | 383 | |
1b8e0e87 | 384 | dit(bf(outgoing chmod)) This parameter allows you to specify a set of |
c094d932 WD |
385 | comma-separated chmod strings that will affect the permissions of all |
386 | outgoing files (files that are being sent out from the daemon). These | |
387 | changes happen first, making the sent permissions appear to be different | |
2243a935 WD |
388 | than those stored in the filesystem itself. For instance, you could |
389 | disable group write permissions on the server while having it appear to | |
390 | be on to the clients. | |
fa3e4a05 WD |
391 | See the description of the bf(--chmod) rsync option and the bf(chmod)(1) |
392 | manpage for information on the format of this string. | |
17af842d | 393 | |
1b8e0e87 | 394 | dit(bf(auth users)) This parameter specifies a comma and |
553f9375 | 395 | space-separated list of usernames that will be allowed to connect to |
5d78a102 AT |
396 | this module. The usernames do not need to exist on the local |
397 | system. The usernames may also contain shell wildcard characters. If | |
398 | "auth users" is set then the client will be challenged to supply a | |
399 | username and password to connect to the module. A challenge response | |
400 | authentication protocol is used for this exchange. The plain text | |
9aacb4df | 401 | usernames and passwords are stored in the file specified by the |
1b8e0e87 | 402 | "secrets file" parameter. The default is for all users to be able to |
41059f75 AT |
403 | connect without a password (this is called "anonymous rsync"). |
404 | ||
d90338ce | 405 | See also the "CONNECTING TO AN RSYNC DAEMON OVER A REMOTE SHELL |
19826af5 | 406 | PROGRAM" section in bf(rsync)(1) for information on how handle an |
bef49340 | 407 | rsyncd.conf-level username that differs from the remote-shell-level |
d90338ce | 408 | username when using a remote shell to connect to an rsync daemon. |
bef49340 | 409 | |
1b8e0e87 | 410 | dit(bf(secrets file)) This parameter specifies the name of |
41059f75 AT |
411 | a file that contains the username:password pairs used for |
412 | authenticating this module. This file is only consulted if the "auth | |
1b8e0e87 | 413 | users" parameter is specified. The file is line based and contains |
41059f75 AT |
414 | username:password pairs separated by a single colon. Any line starting |
415 | with a hash (#) is considered a comment and is skipped. The passwords | |
416 | can contain any characters but be warned that many operating systems | |
417 | limit the length of passwords that can be typed at the client end, so | |
f97c2d4a | 418 | you may find that passwords longer than 8 characters don't work. |
41059f75 | 419 | |
1b8e0e87 | 420 | There is no default for the "secrets file" parameter, you must choose a name |
205c27ac DD |
421 | (such as tt(/etc/rsyncd.secrets)). The file must normally not be readable |
422 | by "other"; see "strict modes". | |
3ca8e68f | 423 | |
1b8e0e87 | 424 | dit(bf(strict modes)) This parameter determines whether or not |
3ca8e68f | 425 | the permissions on the secrets file will be checked. If "strict modes" is |
58811a0a | 426 | true, then the secrets file must not be readable by any user ID other |
3ca8e68f | 427 | than the one that the rsync daemon is running under. If "strict modes" is |
1b8e0e87 | 428 | false, the check is not performed. The default is true. This parameter |
3ca8e68f | 429 | was added to accommodate rsync running on the Windows operating system. |
41059f75 | 430 | |
1b8e0e87 | 431 | dit(bf(hosts allow)) This parameter allows you to specify a |
41059f75 AT |
432 | list of patterns that are matched against a connecting clients |
433 | hostname and IP address. If none of the patterns match then the | |
434 | connection is rejected. | |
435 | ||
436 | Each pattern can be in one of five forms: | |
437 | ||
b8a6dae0 | 438 | quote(itemization( |
61ca7d59 DD |
439 | it() a dotted decimal IPv4 address of the form a.b.c.d, or an IPv6 address |
440 | of the form a:b:c::d:e:f. In this case the incoming machine's IP address | |
bc2b4963 | 441 | must match exactly. |
61ca7d59 DD |
442 | it() an address/mask in the form ipaddr/n where ipaddr is the IP address |
443 | and n is the number of one bits in the netmask. All IP addresses which | |
444 | match the masked IP address will be allowed in. | |
61ca7d59 DD |
445 | it() an address/mask in the form ipaddr/maskaddr where ipaddr is the |
446 | IP address and maskaddr is the netmask in dotted decimal notation for IPv4, | |
447 | or similar for IPv6, e.g. ffff:ffff:ffff:ffff:: instead of /64. All IP | |
448 | addresses which match the masked IP address will be allowed in. | |
41059f75 | 449 | it() a hostname. The hostname as determined by a reverse lookup will |
5315b793 | 450 | be matched (case insensitive) against the pattern. Only an exact |
41059f75 | 451 | match is allowed in. |
41059f75 AT |
452 | it() a hostname pattern using wildcards. These are matched using the |
453 | same rules as normal unix filename matching. If the pattern matches | |
5315b793 | 454 | then the client is allowed in. |
faa82484 | 455 | )) |
41059f75 | 456 | |
61ca7d59 DD |
457 | Note IPv6 link-local addresses can have a scope in the address specification: |
458 | ||
faa82484 WD |
459 | quote( |
460 | tt( fe80::1%link1)nl() | |
461 | tt( fe80::%link1/64)nl() | |
462 | tt( fe80::%link1/ffff:ffff:ffff:ffff::)nl() | |
463 | ) | |
61ca7d59 | 464 | |
41059f75 | 465 | You can also combine "hosts allow" with a separate "hosts deny" |
1b8e0e87 | 466 | parameter. If both parameters are specified then the "hosts allow" parameter is |
5315b793 | 467 | checked first and a match results in the client being able to |
1b8e0e87 | 468 | connect. The "hosts deny" parameter is then checked and a match means |
f97c2d4a | 469 | that the host is rejected. If the host does not match either the |
41059f75 AT |
470 | "hosts allow" or the "hosts deny" patterns then it is allowed to |
471 | connect. | |
472 | ||
1b8e0e87 | 473 | The default is no "hosts allow" parameter, which means all hosts can connect. |
41059f75 | 474 | |
1b8e0e87 | 475 | dit(bf(hosts deny)) This parameter allows you to specify a |
41059f75 AT |
476 | list of patterns that are matched against a connecting clients |
477 | hostname and IP address. If the pattern matches then the connection is | |
1b8e0e87 | 478 | rejected. See the "hosts allow" parameter for more information. |
41059f75 | 479 | |
1b8e0e87 | 480 | The default is no "hosts deny" parameter, which means all hosts can connect. |
41059f75 | 481 | |
1b8e0e87 | 482 | dit(bf(ignore errors)) This parameter tells rsyncd to |
d90338ce | 483 | ignore I/O errors on the daemon when deciding whether to run the delete |
faa82484 | 484 | phase of the transfer. Normally rsync skips the bf(--delete) step if any |
ae283632 | 485 | I/O errors have occurred in order to prevent disastrous deletion due |
58811a0a | 486 | to a temporary resource shortage or other I/O error. In some cases this |
1b8e0e87 | 487 | test is counter productive so you can use this parameter to turn off this |
f97c2d4a | 488 | behavior. |
cda2ae84 | 489 | |
d90338ce | 490 | dit(bf(ignore nonreadable)) This tells the rsync daemon to completely |
78043d19 AT |
491 | ignore files that are not readable by the user. This is useful for |
492 | public archives that may have some non-readable files among the | |
493 | directories, and the sysadmin doesn't want those files to be seen at all. | |
494 | ||
1b8e0e87 | 495 | dit(bf(transfer logging)) This parameter enables per-file |
81791cfc | 496 | logging of downloads and uploads in a format somewhat similar to that |
d90338ce | 497 | used by ftp daemons. The daemon always logs the transfer at the end, so |
3b2bebbf WD |
498 | if a transfer is aborted, no mention will be made in the log file. |
499 | ||
1b8e0e87 | 500 | If you want to customize the log lines, see the "log format" parameter. |
81791cfc | 501 | |
1b8e0e87 | 502 | dit(bf(log format)) This parameter allows you to specify the |
9e453674 WD |
503 | format used for logging file transfers when transfer logging is enabled. |
504 | The format is a text string containing embedded single-character escape | |
80a24d52 WD |
505 | sequences prefixed with a percent (%) character. An optional numeric |
506 | field width may also be specified between the percent and the escape | |
0abe148f | 507 | letter (e.g. "bf(%-50n %8l %07p)"). |
81791cfc | 508 | |
9e453674 | 509 | The default log format is "%o %h [%a] %m (%u) %f %l", and a "%t [%p] " |
1b8e0e87 | 510 | is always prefixed when using the "log file" parameter. |
9e453674 WD |
511 | (A perl script that will summarize this default log format is included |
512 | in the rsync source code distribution in the "support" subdirectory: | |
513 | rsyncstats.) | |
514 | ||
515 | The single-character escapes that are understood are as follows: | |
81791cfc | 516 | |
b8a6dae0 | 517 | quote(itemization( |
aca5500a | 518 | it() %a the remote IP address |
f97c2d4a | 519 | it() %b the number of bytes actually transferred |
aca5500a | 520 | it() %B the permission bits of the file (e.g. rwxrwxrwt) |
886df221 WD |
521 | it() %c the total size of the block checksums received for the basis file (only when sending) |
522 | it() %C the full-file MD5 checksum if bf(--checksum) is enabled or a file was transferred (only for protocol 30 or above). | |
aca5500a WD |
523 | it() %f the filename (long form on sender; no trailing "/") |
524 | it() %G the gid of the file (decimal) or "DEFAULT" | |
525 | it() %h the remote host name | |
527a010f | 526 | it() %i an itemized list of what is being updated |
aca5500a WD |
527 | it() %l the length of the file in bytes |
528 | it() %L the string " -> SYMLINK", " => HARDLINK", or "" (where bf(SYMLINK) or bf(HARDLINK) is a filename) | |
529 | it() %m the module name | |
530 | it() %M the last-modified time of the file | |
531 | it() %n the filename (short form; trailing "/" on dir) | |
532 | it() %o the operation, which is "send", "recv", or "del." (the latter includes the trailing period) | |
533 | it() %p the process ID of this rsync session | |
534 | it() %P the module path | |
535 | it() %t the current date time | |
536 | it() %u the authenticated username or an empty string | |
537 | it() %U the uid of the file (decimal) | |
faa82484 | 538 | )) |
81791cfc | 539 | |
9e453674 WD |
540 | For a list of what the characters mean that are output by "%i", see the |
541 | bf(--itemize-changes) option in the rsync manpage. | |
527a010f | 542 | |
9e453674 | 543 | Note that some of the logged output changes when talking with older |
80a24d52 | 544 | rsync versions. For instance, deleted files were only output as verbose |
8ebdc972 | 545 | messages prior to rsync 2.6.4. |
a85a1514 | 546 | |
1b8e0e87 WD |
547 | dit(bf(timeout)) This parameter allows you to override the |
548 | clients choice for I/O timeout for this module. Using this parameter you | |
81791cfc AT |
549 | can ensure that rsync won't wait on a dead client forever. The timeout |
550 | is specified in seconds. A value of zero means no timeout and is the | |
d90338ce | 551 | default. A good choice for anonymous rsync daemons may be 600 (giving |
81791cfc AT |
552 | a 10 minute timeout). |
553 | ||
1b8e0e87 | 554 | dit(bf(refuse options)) This parameter allows you to |
553f9375 | 555 | specify a space-separated list of rsync command line options that will |
d90338ce | 556 | be refused by your rsync daemon. |
1cb0a3ed WD |
557 | You may specify the full option name, its one-letter abbreviation, or a |
558 | wild-card string that matches multiple options. | |
9eef8f0b WD |
559 | For example, this would refuse bf(--checksum) (bf(-c)) and all the various |
560 | delete options: | |
1cb0a3ed | 561 | |
9eef8f0b WD |
562 | quote(tt( refuse options = c delete)) |
563 | ||
564 | The reason the above refuses all delete options is that the options imply | |
565 | bf(--delete), and implied options are refused just like explicit options. | |
e1636830 | 566 | As an additional safety feature, the refusal of "delete" also refuses |
0b52f94d | 567 | bf(remove-source-files) when the daemon is the sender; if you want the latter |
e1636830 | 568 | without the former, instead refuse "delete-*" -- that refuses all the |
0b52f94d | 569 | delete modes without affecting bf(--remove-source-files). |
1cb0a3ed | 570 | |
d90338ce | 571 | When an option is refused, the daemon prints an error message and exits. |
f97c2d4a WD |
572 | To prevent all compression when serving files, |
573 | you can use "dont compress = *" (see below) | |
63f0774f DD |
574 | instead of "refuse options = compress" to avoid returning an error to a |
575 | client that requests compression. | |
cd8185f2 | 576 | |
1b8e0e87 | 577 | dit(bf(dont compress)) This parameter allows you to select |
83fff1aa | 578 | filenames based on wildcard patterns that should not be compressed |
1b8e0e87 | 579 | when pulling files from the daemon (no analogous parameter exists to |
f97c2d4a WD |
580 | govern the pushing of files to a daemon). |
581 | Compression is expensive in terms of CPU usage, so it | |
83fff1aa | 582 | is usually good to not try to compress files that won't compress well, |
f97c2d4a | 583 | such as already compressed files. |
83fff1aa | 584 | |
1b8e0e87 | 585 | The "dont compress" parameter takes a space-separated list of |
83fff1aa AT |
586 | case-insensitive wildcard patterns. Any source filename matching one |
587 | of the patterns will not be compressed during transfer. | |
588 | ||
1b8e0e87 | 589 | See the bf(--skip-compress) parameter in the bf(rsync)(1) manpage for the list |
34ca58d4 | 590 | of file suffixes that are not compressed by default. Specifying a value |
1b8e0e87 | 591 | for the "dont compress" parameter changes the default when the daemon is |
34ca58d4 | 592 | the sender. |
83fff1aa | 593 | |
c20936b8 WD |
594 | dit(bf(pre-xfer exec), bf(post-xfer exec)) You may specify a command to be run |
595 | before and/or after the transfer. If the bf(pre-xfer exec) command fails, the | |
596 | transfer is aborted before it begins. | |
597 | ||
37439b36 WD |
598 | The following environment variables will be set, though some are |
599 | specific to the pre-xfer or the post-xfer environment: | |
c20936b8 | 600 | |
b8a6dae0 | 601 | quote(itemization( |
c20936b8 WD |
602 | it() bf(RSYNC_MODULE_NAME): The name of the module being accessed. |
603 | it() bf(RSYNC_MODULE_PATH): The path configured for the module. | |
604 | it() bf(RSYNC_HOST_ADDR): The accessing host's IP address. | |
605 | it() bf(RSYNC_HOST_NAME): The accessing host's name. | |
606 | it() bf(RSYNC_USER_NAME): The accessing user's name (empty if no user). | |
a739128d | 607 | it() bf(RSYNC_PID): A unique number for this transfer. |
37439b36 WD |
608 | it() bf(RSYNC_REQUEST): (pre-xfer only) The module/path info specified |
609 | by the user (note that the user can specify multiple source files, | |
610 | so the request can be something like "mod/path1 mod/path2", etc.). | |
70e98a43 | 611 | it() bf(RSYNC_ARG#): (pre-xfer only) The pre-request arguments are set |
fddf529d WD |
612 | in these numbered values. RSYNC_ARG0 is always "rsyncd", and the last |
613 | value contains a single period. | |
a6333519 WD |
614 | it() bf(RSYNC_EXIT_STATUS): (post-xfer only) the server side's exit value. |
615 | This will be 0 for a successful run, a positive value for an error that the | |
616 | server generated, or a -1 if rsync failed to exit properly. Note that an | |
617 | error that occurs on the client side does not currently get sent to the | |
618 | server side, so this is not the final exit status for the whole transfer. | |
19826af5 | 619 | it() bf(RSYNC_RAW_STATUS): (post-xfer only) the raw exit value from code(waitpid()). |
c20936b8 WD |
620 | )) |
621 | ||
622 | Even though the commands can be associated with a particular module, they | |
623 | are run using the permissions of the user that started the daemon (not the | |
37439b36 | 624 | module's uid/gid setting) without any chroot restrictions. |
c20936b8 | 625 | |
41059f75 AT |
626 | enddit() |
627 | ||
8a3ddcfc WD |
628 | manpagesection(CONFIG DIRECTIVES) |
629 | ||
630 | There are currently two config directives available that allow a config file to | |
631 | incorporate the contents of other files: bf(&include) and bf(&merge). Both | |
632 | allow a reference to either a file or a directory. They differ in how | |
582831a4 WD |
633 | segregated the file's contents are considered to be. |
634 | ||
635 | The bf(&include) directive treats each file as more distinct, with each one | |
636 | inheriting the defaults of the parent file, starting the parameter parsing | |
637 | as globals/defaults, and leaving the defaults unchanged for the parsing of | |
638 | the rest of the parent file. | |
639 | ||
640 | The bf(&merge) directive, on the other hand, treats the file's contents as | |
641 | if it were simply inserted in place of the directive, and thus it can set | |
642 | parameters in a module started in another file, can affect the defaults for | |
643 | other files, etc. | |
8a3ddcfc WD |
644 | |
645 | When an bf(&include) or bf(&merge) directive refers to a directory, it will read | |
646 | in all the bf(*.conf) files contained inside that directory (without any | |
647 | recursive scanning), with the files sorted into alpha order. So, if you have a | |
648 | directory named "rsyncd.d" with the files "foo.conf", "bar.conf", and | |
649 | "baz.conf" inside it, this directive: | |
650 | ||
582831a4 | 651 | verb( &include /path/rsyncd.d ) |
8a3ddcfc WD |
652 | |
653 | would be the same as this set of directives: | |
654 | ||
582831a4 WD |
655 | verb( &include /path/rsyncd.d/bar.conf |
656 | &include /path/rsyncd.d/baz.conf | |
657 | &include /path/rsyncd.d/foo.conf ) | |
8a3ddcfc WD |
658 | |
659 | except that it adjusts as files are added and removed from the directory. | |
660 | ||
661 | The advantage of the bf(&include) directive is that you can define one or more | |
582831a4 WD |
662 | modules in a separate file without worrying about unintended side-effects |
663 | between the self-contained module files. For instance, this is a useful | |
664 | /etc/rsyncd.conf file: | |
8a3ddcfc WD |
665 | |
666 | verb( port = 873 | |
582831a4 | 667 | log file = /var/log/rsync.log |
8a3ddcfc WD |
668 | pid file = /var/lock/rsync.lock |
669 | ||
670 | &include /etc/rsyncd.d ) | |
671 | ||
672 | The advantage of the bf(&merge) directive is that you can load config snippets | |
673 | that can be included into multiple module definitions. | |
674 | ||
4c3d16be AT |
675 | manpagesection(AUTHENTICATION STRENGTH) |
676 | ||
677 | The authentication protocol used in rsync is a 128 bit MD4 based | |
2b7e1292 WD |
678 | challenge response system. This is fairly weak protection, though (with |
679 | at least one brute-force hash-finding algorithm publicly available), so | |
680 | if you want really top-quality security, then I recommend that you run | |
681 | rsync over ssh. (Yes, a future version of rsync will switch over to a | |
682 | stronger hashing method.) | |
4c3d16be | 683 | |
d90338ce | 684 | Also note that the rsync daemon protocol does not currently provide any |
f39281ae | 685 | encryption of the data that is transferred over the connection. Only |
4c3d16be AT |
686 | authentication is provided. Use ssh as the transport if you want |
687 | encryption. | |
688 | ||
689 | Future versions of rsync may support SSL for better authentication and | |
690 | encryption, but that is still being investigated. | |
691 | ||
41059f75 AT |
692 | manpagesection(EXAMPLES) |
693 | ||
694 | A simple rsyncd.conf file that allow anonymous rsync to a ftp area at | |
e22de162 | 695 | tt(/home/ftp) would be: |
41059f75 AT |
696 | |
697 | verb( | |
698 | [ftp] | |
e22de162 AT |
699 | path = /home/ftp |
700 | comment = ftp export area | |
41059f75 AT |
701 | ) |
702 | ||
41059f75 AT |
703 | A more sophisticated example would be: |
704 | ||
faa82484 WD |
705 | verb( |
706 | uid = nobody | |
707 | gid = nobody | |
2fe1feea | 708 | use chroot = yes |
faa82484 WD |
709 | max connections = 4 |
710 | syslog facility = local5 | |
0f621785 | 711 | pid file = /var/run/rsyncd.pid |
41059f75 | 712 | |
faa82484 | 713 | [ftp] |
2fe1feea | 714 | path = /var/ftp/./pub |
41059f75 AT |
715 | comment = whole ftp area (approx 6.1 GB) |
716 | ||
717 | [sambaftp] | |
2fe1feea | 718 | path = /var/ftp/./pub/samba |
41059f75 AT |
719 | comment = Samba ftp area (approx 300 MB) |
720 | ||
721 | [rsyncftp] | |
2fe1feea | 722 | path = /var/ftp/./pub/rsync |
41059f75 | 723 | comment = rsync ftp area (approx 6 MB) |
f97c2d4a | 724 | |
41059f75 AT |
725 | [sambawww] |
726 | path = /public_html/samba | |
727 | comment = Samba WWW pages (approx 240 MB) | |
728 | ||
729 | [cvs] | |
730 | path = /data/cvs | |
731 | comment = CVS repository (requires authentication) | |
732 | auth users = tridge, susan | |
733 | secrets file = /etc/rsyncd.secrets | |
734 | ) | |
735 | ||
736 | The /etc/rsyncd.secrets file would look something like this: | |
737 | ||
faa82484 WD |
738 | quote( |
739 | tt(tridge:mypass)nl() | |
740 | tt(susan:herpass)nl() | |
741 | ) | |
41059f75 AT |
742 | |
743 | manpagefiles() | |
744 | ||
30e8c8e1 | 745 | /etc/rsyncd.conf or rsyncd.conf |
41059f75 AT |
746 | |
747 | manpageseealso() | |
748 | ||
b8a6dae0 | 749 | bf(rsync)(1) |
41059f75 AT |
750 | |
751 | manpagediagnostics() | |
752 | ||
753 | manpagebugs() | |
754 | ||
41059f75 | 755 | Please report bugs! The rsync bug tracking system is online at |
9e3c856a | 756 | url(http://rsync.samba.org/)(http://rsync.samba.org/) |
41059f75 AT |
757 | |
758 | manpagesection(VERSION) | |
d90338ce | 759 | |
db8f3f73 | 760 | This man page is current for version 3.0.3 of rsync. |
41059f75 AT |
761 | |
762 | manpagesection(CREDITS) | |
763 | ||
764 | rsync is distributed under the GNU public license. See the file | |
765 | COPYING for details. | |
766 | ||
767 | The primary ftp site for rsync is | |
9e3c856a | 768 | url(ftp://rsync.samba.org/pub/rsync)(ftp://rsync.samba.org/pub/rsync). |
41059f75 AT |
769 | |
770 | A WEB site is available at | |
9e3c856a | 771 | url(http://rsync.samba.org/)(http://rsync.samba.org/) |
41059f75 AT |
772 | |
773 | We would be delighted to hear from you if you like this program. | |
774 | ||
775 | This program uses the zlib compression library written by Jean-loup | |
776 | Gailly and Mark Adler. | |
777 | ||
778 | manpagesection(THANKS) | |
779 | ||
780 | Thanks to Warren Stanley for his original idea and patch for the rsync | |
d90338ce | 781 | daemon. Thanks to Karsten Thygesen for his many suggestions and |
f97c2d4a | 782 | documentation! |
41059f75 AT |
783 | |
784 | manpageauthor() | |
785 | ||
ae283632 WD |
786 | rsync was written by Andrew Tridgell and Paul Mackerras. |
787 | Many people have later contributed to it. | |
41059f75 | 788 | |
ae283632 | 789 | Mailing lists for support and development are available at |
f97c2d4a | 790 | url(http://lists.samba.org)(lists.samba.org) |