Commit | Line | Data |
---|---|---|
9e3c856a | 1 | mailto(rsync-bugs@samba.org) |
651443a7 | 2 | manpage(rsyncd.conf)(5)(12 Feb 1999)()() |
41059f75 AT |
3 | manpagename(rsyncd.conf)(configuration file for rsync server) |
4 | manpagesynopsis() | |
5 | ||
6 | rsyncd.conf | |
7 | ||
8 | manpagedescription() | |
9 | ||
10 | The rsyncd.conf file is the runtime configuration file for rsync when | |
e22de162 | 11 | run with the --daemon option. When run in this way rsync becomes a |
41059f75 AT |
12 | rsync server listening on TCP port 873. Connections from rsync clients |
13 | are accepted for either anonymous or authenticated rsync sessions. | |
14 | ||
15 | The rsyncd.conf file controls authentication, access, logging and | |
16 | available modules. | |
17 | ||
18 | manpagesection(FILE FORMAT) | |
19 | ||
20 | The file consists of modules and parameters. A module begins with the | |
21 | name of the module in square brackets and continues until the next | |
22 | module begins. Modules contain parameters of the form 'name = value'. | |
23 | ||
24 | The file is line-based - that is, each newline-terminated line represents | |
25 | either a comment, a module name or a parameter. | |
26 | ||
27 | Only the first equals sign in a parameter is significant. Whitespace before | |
28 | or after the first equals sign is discarded. Leading, trailing and internal | |
29 | whitespace in module and parameter names is irrelevant. Leading and | |
30 | trailing whitespace in a parameter value is discarded. Internal whitespace | |
31 | within a parameter value is retained verbatim. | |
32 | ||
33 | Any line beginning with a hash (#) is ignored, as are lines containing | |
34 | only whitespace. | |
35 | ||
e22de162 | 36 | Any line ending in a \ is "continued" on the next line in the |
41059f75 AT |
37 | customary UNIX fashion. |
38 | ||
39 | The values following the equals sign in parameters are all either a string | |
40 | (no quotes needed) or a boolean, which may be given as yes/no, 0/1 or | |
41 | true/false. Case is not significant in boolean values, but is preserved | |
42 | in string values. | |
43 | ||
5315b793 | 44 | manpagesection(LAUNCHING THE RSYNC DAEMON) |
41059f75 AT |
45 | |
46 | The rsync daemon is launched by specifying the --daemon option to | |
5315b793 | 47 | rsync. The daemon must run with root privileges. |
41059f75 | 48 | |
14d43f1f | 49 | You can launch it either via inetd or as a stand-alone daemon. If run |
e22de162 | 50 | as a daemon then just run the command "rsync --daemon" from a suitable |
41059f75 AT |
51 | startup script. |
52 | ||
53 | When run via inetd you should add a line like this to /etc/services: | |
54 | ||
e22de162 | 55 | quote(rsync 873/tcp) |
41059f75 | 56 | |
e22de162 | 57 | and a single line something like this to /etc/inetd.conf: |
41059f75 | 58 | |
e22de162 | 59 | quote(rsync stream tcp nowait root /usr/bin/rsync rsyncd --daemon) |
41059f75 | 60 | |
79f118d8 DD |
61 | Replace "/usr/bin/rsync" with the path to where you have rsync installed on |
62 | your system. You will then need to send inetd a HUP signal to tell it to | |
63 | reread its config file. | |
41059f75 AT |
64 | |
65 | Note that you should not send the rsync server a HUP signal to force | |
e22de162 | 66 | it to reread the tt(/etc/rsyncd.conf). The file is re-read on each client |
41059f75 AT |
67 | connection. |
68 | ||
69 | manpagesection(GLOBAL OPTIONS) | |
70 | ||
71 | The first parameters in the file (before a [module] header) are the | |
72 | global parameters. | |
73 | ||
74 | You may also include any module parameters in the global part of the | |
75 | config file in which case the supplied value will override the | |
76 | default for that parameter. | |
77 | ||
78 | startdit() | |
79 | dit(bf(motd file)) The "motd file" option allows you to specify a | |
5315b793 | 80 | "message of the day" to display to clients on each connect. This |
41059f75 AT |
81 | usually contains site information and any legal notices. The default |
82 | is no motd file. | |
83 | ||
37863201 AT |
84 | dit(bf(log file)) The "log file" option tells the rsync daemon to log |
85 | messages to that file rather than using syslog. This is particularly | |
86 | useful on systems (such as AIX) where syslog() doesn't work for | |
8638dd48 DD |
87 | chrooted programs. |
88 | ||
89 | dit(bf(pid file)) The "pid file" option tells the rsync daemon to write | |
90 | its process id to that file. | |
37863201 | 91 | |
41059f75 AT |
92 | dit(bf(syslog facility)) The "syslog facility" option allows you to |
93 | specify the syslog facility name to use when logging messages from the | |
94 | rsync server. You may use any standard syslog facility name which is | |
95 | defined on your system. Common names are auth, authpriv, cron, daemon, | |
96 | ftp, kern, lpr, mail, news, security, syslog, user, uucp, local0, | |
97 | local1, local2, local3, local4, local5, local6 and local7. The default | |
98 | is daemon. | |
99 | ||
a6801c39 AT |
100 | dit(bf(socket options)) This option can provide endless fun for people |
101 | who like to tune their systems to the utmost degree. You can set all | |
102 | sorts of socket options which may make transfers faster (or | |
103 | slower!). Read the man page for the setsockopt() system call for | |
104 | details on some of the options you may be able to set. By default no | |
105 | special socket options are set. | |
106 | ||
41059f75 AT |
107 | enddit() |
108 | ||
109 | ||
110 | manpagesection(MODULE OPTIONS) | |
111 | ||
112 | After the global options you should define a number of modules, each | |
113 | module exports a directory tree as a symbolic name. Modules are | |
114 | exported by specifying a module name in square brackets [module] | |
115 | followed by the options for that module. | |
116 | ||
117 | startdit() | |
118 | ||
119 | dit(bf(comment)) The "comment" option specifies a description string | |
120 | that is displayed next to the module name when clients obtain a list | |
121 | of available modules. The default is no comment. | |
122 | ||
123 | dit(bf(path)) The "path" option specifies the directory in the servers | |
8638dd48 DD |
124 | filesystem to make available in this module. You must specify this option |
125 | for each module in tt(/etc/rsyncd.conf). | |
126 | ||
127 | dit(bf(use chroot)) If "use chroot" is true, the rsync server will chroot | |
128 | to the "path" before starting the file transfer with the client. This has | |
129 | the advantage of extra protection against possible implementation security | |
130 | holes, but it has the disadvantages of requiring super-user privileges and | |
131 | of not being able to follow symbolic links outside of the new root path. | |
132 | The default is to use chroot. | |
41059f75 | 133 | |
5e71c444 AT |
134 | dit(bf(max connections)) The "max connections" option allows you to |
135 | specify the maximum number of simultaneous connections you will allow | |
136 | to this module of your rsync server. Any clients connecting when the | |
137 | maximum has been reached will receive a message telling them to try | |
138 | later. The default is 0 which means no limit. | |
139 | ||
140 | dit(bf(lock file)) The "lock file" option specifies the file to use to | |
141 | support the "max connections" option. The rsync server uses record | |
142 | locking on this file to ensure that the max connections limit is not | |
143 | exceeded. The default is tt(/var/run/rsyncd.lock). | |
144 | ||
41059f75 AT |
145 | dit(bf(read only)) The "read only" option determines whether clients |
146 | will be able to upload files or not. If "read only" is true then any | |
147 | attempted uploads will fail. If "read only" is false then uploads will | |
148 | be possible if file permissions on the server allow them. The default | |
149 | is for all modules to be read only. | |
150 | ||
151 | dit(bf(list)) The "list" option determines if this module should be | |
152 | listed when the client asks for a listing of available modules. By | |
153 | setting this to false you can create hidden modules. The default is | |
154 | for modules to be listable. | |
155 | ||
156 | dit(bf(uid)) The "uid" option specifies the user name or user id that | |
716baed7 DD |
157 | file transfers to and from that module should take place as when the daemon |
158 | was run as root. In combination with the "gid" option this determines what | |
159 | file permissions are available. The default is the user "nobody". | |
41059f75 AT |
160 | |
161 | dit(bf(gid)) The "gid" option specifies the group name or group id that | |
716baed7 DD |
162 | file transfers to and from that module should take place as when the daemon |
163 | was run as root. This complements the "uid" option. The default is the | |
164 | group "nobody". | |
41059f75 | 165 | |
8f3a2d54 | 166 | dit(bf(exclude)) The "exclude" option allows you to specify a space |
8dfac376 AT |
167 | separated list of patterns to add to the exclude list. This is |
168 | equivalent to the client specifying these patterns with the --exclude | |
169 | option except that the exclude list is not passed to the client and | |
170 | thus only apply on the server. Only one "exclude" option may be | |
171 | specified, but you can use "-" and "+" before patterns to specify | |
172 | exclude/include. | |
651443a7 DD |
173 | |
174 | Note that this option is not designed with strong security in | |
8f3a2d54 AT |
175 | mind, it is quite possible that a client may find a way to bypass this |
176 | exclude list. If you want to absolutely ensure that certain files | |
177 | cannot be accessed then use the uid/gid options in combination with | |
178 | file permissions. | |
179 | ||
180 | dit(bf(exclude from)) The "exclude from" option specifies a filename | |
181 | on the server that contains exclude patterns, one per line. This is | |
182 | equivalent to the client specifying the --exclude-from option with a | |
8dfac376 AT |
183 | equivalent file except that the resulting exclude patterns are not |
184 | passed to the client and thus only apply on the server. See also the | |
185 | note about security for the exclude option above. | |
8f3a2d54 | 186 | |
cd64343a DD |
187 | dit(bf(include)) The "include" option allows you to specify a space |
188 | separated list of patterns which rsync should not exclude. This is | |
189 | equivalent to the client specifying these patterns with the --include | |
651443a7 DD |
190 | option. This is useful as it allows you to build up quite complex |
191 | exclude/include rules. Only one "include" option may be specified, but you | |
192 | can use "+" and "-" before patterns to switch include/exclude. | |
cd64343a | 193 | |
651443a7 DD |
194 | See the section of exclude patterns in the rsync man page for information |
195 | on the syntax of this option. | |
cd64343a DD |
196 | |
197 | dit(bf(include from)) The "include from" option specifies a filename | |
198 | on the server that contains include patterns, one per line. This is | |
199 | equivalent to the client specifying the --include-from option with a | |
200 | equivalent file. | |
201 | ||
41059f75 AT |
202 | dit(bf(auth users)) The "auth users" option specifies a comma |
203 | and space separated list of usernames that will be allowed to connect | |
204 | to this module. The usernames do not need to exist on the local | |
205 | system. If "auth users" is set then the client will be challenged to | |
206 | supply a username and password to connect to the module. A challenge | |
207 | response authentication protocol is used for this exchange. The plain | |
208 | text usernames are passwords are stored in the file specified by the | |
209 | "secrets file" option. The default is for all users to be able to | |
210 | connect without a password (this is called "anonymous rsync"). | |
211 | ||
212 | dit(bf(secrets file)) The "secrets file" option specifies the name of | |
213 | a file that contains the username:password pairs used for | |
214 | authenticating this module. This file is only consulted if the "auth | |
215 | users" option is specified. The file is line based and contains | |
216 | username:password pairs separated by a single colon. Any line starting | |
217 | with a hash (#) is considered a comment and is skipped. The passwords | |
218 | can contain any characters but be warned that many operating systems | |
219 | limit the length of passwords that can be typed at the client end, so | |
220 | you may find that passwords longer than 8 characters don't work. | |
221 | ||
3ca8e68f DD |
222 | There is no default for the "secrets file" option, you must choose a name |
223 | (such as tt(/etc/rsyncd.secrets)). | |
224 | ||
225 | dit(bf(strict modes)) The "strict modes" option determines whether or not | |
226 | the permissions on the secrets file will be checked. If "strict modes" is | |
227 | true, then the secrets file must not be readable by any user id other | |
228 | than the one that the rsync daemon is running under. If "strict modes" is | |
229 | false, the check is not performed. The default is true. This option | |
230 | was added to accommodate rsync running on the Windows operating system. | |
41059f75 AT |
231 | |
232 | dit(bf(hosts allow)) The "hosts allow" option allows you to specify a | |
233 | list of patterns that are matched against a connecting clients | |
234 | hostname and IP address. If none of the patterns match then the | |
235 | connection is rejected. | |
236 | ||
237 | Each pattern can be in one of five forms: | |
238 | ||
239 | itemize( | |
240 | it() a dotted decimal IP address. In this case the incoming machines | |
241 | IP address must match exactly. | |
242 | ||
243 | it() a address/mask in the form a.b.c.d/n were n is the number of | |
244 | one bits in in the netmask. All IP addresses which match the masked | |
245 | IP address will be allowed in. | |
246 | ||
247 | it() a address/mask in the form a.b.c.d/e.f.g.h where e.f.g.h is a | |
5315b793 | 248 | netmask in dotted decimal notation. All IP addresses which match the masked |
41059f75 AT |
249 | IP address will be allowed in. |
250 | ||
251 | it() a hostname. The hostname as determined by a reverse lookup will | |
5315b793 | 252 | be matched (case insensitive) against the pattern. Only an exact |
41059f75 AT |
253 | match is allowed in. |
254 | ||
255 | it() a hostname pattern using wildcards. These are matched using the | |
256 | same rules as normal unix filename matching. If the pattern matches | |
5315b793 | 257 | then the client is allowed in. |
41059f75 AT |
258 | ) |
259 | ||
260 | You can also combine "hosts allow" with a separate "hosts deny" | |
261 | option. If both options are specified then the "hosts allow" option s | |
5315b793 | 262 | checked first and a match results in the client being able to |
41059f75 AT |
263 | connect. The "hosts deny" option is then checked and a match means |
264 | that the host is rejected. If the host does not match either the | |
265 | "hosts allow" or the "hosts deny" patterns then it is allowed to | |
266 | connect. | |
267 | ||
268 | The default is no "hosts allow" option, which means all hosts can connect. | |
269 | ||
de2fd20e | 270 | dit(bf(hosts deny)) The "hosts deny" option allows you to specify a |
41059f75 AT |
271 | list of patterns that are matched against a connecting clients |
272 | hostname and IP address. If the pattern matches then the connection is | |
273 | rejected. See the "hosts allow" option for more information. | |
274 | ||
275 | The default is no "hosts deny" option, which means all hosts can connect. | |
276 | ||
cda2ae84 AT |
277 | dit(bf(ignore errors)) The "ignore errors" option tells rsyncd to |
278 | ignore IO errors on the server when deciding whether to run the delete | |
279 | phase of the transfer. Normally rsync skips the --delete step if any | |
280 | IO errors have occurred in order to prevent disasterous deletion due | |
281 | to a temporary resource shortage or other IO error. In some cases this | |
282 | test is counter productive so you can use this option to turn off this | |
283 | behaviour. | |
284 | ||
81791cfc AT |
285 | dit(bf(transfer logging)) The "transfer logging" option enables per-file |
286 | logging of downloads and uploads in a format somewhat similar to that | |
14d43f1f | 287 | used by ftp daemons. If you want to customize the log formats look at |
81791cfc AT |
288 | the log format option. |
289 | ||
290 | dit(bf(log format)) The "log format" option allows you to specify the | |
291 | format used for logging file transfers when transfer logging is | |
292 | enabled. The format is a text string containing embedded single | |
293 | character escape sequences prefixed with a percent (%) character. | |
294 | ||
295 | The prefixes that are understood are: | |
296 | ||
297 | itemize( | |
298 | it() %h for the remote host name | |
299 | it() %a for the remote IP address | |
300 | it() %l for the length of the file in bytes | |
301 | it() %p for the process id of this rsync session | |
302 | it() %o for the operation, which is either "send" or "recv" | |
303 | it() %f for the filename | |
304 | it() %P for the module path | |
305 | it() %m for the module name | |
b882b497 | 306 | it() %t for the current date time |
81791cfc AT |
307 | it() %u for the authenticated username (or the null string) |
308 | it() %b for the number of bytes actually transferred | |
309 | it() %c when sending files this gives the number of checksum bytes | |
310 | received for this file | |
311 | ) | |
312 | ||
b882b497 DD |
313 | The default log format is "%o %h [%a] %m (%u) %f %l", and a "%t [%p] " |
314 | is always added to the beginning when using the "log file" option. | |
81791cfc | 315 | |
14d43f1f | 316 | A perl script called rsyncstats to summarize this format is included |
81791cfc AT |
317 | in the rsync source code distribution. |
318 | ||
319 | dit(bf(timeout)) The "timeout" option allows you to override the | |
14d43f1f | 320 | clients choice for IO timeout for this module. Using this option you |
81791cfc AT |
321 | can ensure that rsync won't wait on a dead client forever. The timeout |
322 | is specified in seconds. A value of zero means no timeout and is the | |
323 | default. A good choice for anonymous rsync servers may be 600 (giving | |
324 | a 10 minute timeout). | |
325 | ||
cd8185f2 AT |
326 | dit(bf(refuse options)) The "refuse options" option allows you to |
327 | specify a space separated list of rsync command line options that will | |
63f0774f DD |
328 | be refused by your rsync server. The full names of the options must be |
329 | used (i.e., you must use "checksum" not "c" to disable checksumming). | |
330 | When an option is refused, the server prints an error message and exits. | |
331 | To prevent all compression, you can use "dont compress = *" (see below) | |
332 | instead of "refuse options = compress" to avoid returning an error to a | |
333 | client that requests compression. | |
cd8185f2 | 334 | |
83fff1aa AT |
335 | dit(bf(dont compress)) The "dont compress" option allows you to select |
336 | filenames based on wildcard patterns that should not be compressed | |
337 | during transfer. Compression is expensive in terms of CPU usage so it | |
338 | is usually good to not try to compress files that won't compress well, | |
339 | such as already compressed files. | |
340 | ||
341 | The "dont compress" option takes a space separated list of | |
342 | case-insensitive wildcard patterns. Any source filename matching one | |
343 | of the patterns will not be compressed during transfer. | |
344 | ||
345 | The default setting is verb(*.gz *.tgz *.zip *.z *.rpm *.deb) | |
346 | ||
41059f75 AT |
347 | enddit() |
348 | ||
4c3d16be AT |
349 | manpagesection(AUTHENTICATION STRENGTH) |
350 | ||
351 | The authentication protocol used in rsync is a 128 bit MD4 based | |
352 | challenge response system. Although I believe that no one has ever | |
353 | demonstrated a brute-force break of this sort of system you should | |
14d43f1f | 354 | realize that this is not a "military strength" authentication system. |
4c3d16be AT |
355 | It should be good enough for most purposes but if you want really top |
356 | quality security then I recommend that you run rsync over ssh. | |
357 | ||
358 | Also note that the rsync server protocol does not currently provide any | |
359 | encryption of the data that is transferred over the link. Only | |
360 | authentication is provided. Use ssh as the transport if you want | |
361 | encryption. | |
362 | ||
363 | Future versions of rsync may support SSL for better authentication and | |
364 | encryption, but that is still being investigated. | |
365 | ||
41059f75 AT |
366 | manpagesection(EXAMPLES) |
367 | ||
368 | A simple rsyncd.conf file that allow anonymous rsync to a ftp area at | |
e22de162 | 369 | tt(/home/ftp) would be: |
41059f75 AT |
370 | |
371 | verb( | |
372 | [ftp] | |
e22de162 AT |
373 | path = /home/ftp |
374 | comment = ftp export area | |
41059f75 AT |
375 | ) |
376 | ||
377 | ||
378 | A more sophisticated example would be: | |
379 | ||
e22de162 AT |
380 | uid = nobody nl() |
381 | gid = nobody nl() | |
8638dd48 | 382 | use chroot = no nl() |
e22de162 AT |
383 | max connections = 4 nl() |
384 | syslog facility = local5 nl() | |
8638dd48 | 385 | pid file = /etc/rsyncd.pid |
41059f75 | 386 | |
e22de162 | 387 | verb([ftp] |
41059f75 AT |
388 | path = /var/ftp/pub |
389 | comment = whole ftp area (approx 6.1 GB) | |
390 | ||
391 | [sambaftp] | |
392 | path = /var/ftp/pub/samba | |
393 | comment = Samba ftp area (approx 300 MB) | |
394 | ||
395 | [rsyncftp] | |
396 | path = /var/ftp/pub/rsync | |
397 | comment = rsync ftp area (approx 6 MB) | |
398 | ||
399 | [sambawww] | |
400 | path = /public_html/samba | |
401 | comment = Samba WWW pages (approx 240 MB) | |
402 | ||
403 | [cvs] | |
404 | path = /data/cvs | |
405 | comment = CVS repository (requires authentication) | |
406 | auth users = tridge, susan | |
407 | secrets file = /etc/rsyncd.secrets | |
408 | ) | |
409 | ||
410 | The /etc/rsyncd.secrets file would look something like this: | |
411 | ||
e22de162 | 412 | tridge:mypass nl() |
41059f75 | 413 | susan:herpass |
41059f75 AT |
414 | |
415 | manpagefiles() | |
416 | ||
417 | /etc/rsyncd.conf | |
418 | ||
419 | manpageseealso() | |
420 | ||
421 | rsync(1) | |
422 | ||
423 | manpagediagnostics() | |
424 | ||
425 | manpagebugs() | |
426 | ||
427 | The rsync server does not send all types of error messages to the | |
428 | client. this means a client may be mystified as to why a transfer | |
429 | failed. The error will have been logged by syslog on the server. | |
430 | ||
431 | Please report bugs! The rsync bug tracking system is online at | |
9e3c856a | 432 | url(http://rsync.samba.org/)(http://rsync.samba.org/) |
41059f75 AT |
433 | |
434 | manpagesection(VERSION) | |
435 | This man page is current for version 2.0 of rsync | |
436 | ||
437 | manpagesection(CREDITS) | |
438 | ||
439 | rsync is distributed under the GNU public license. See the file | |
440 | COPYING for details. | |
441 | ||
442 | The primary ftp site for rsync is | |
9e3c856a | 443 | url(ftp://rsync.samba.org/pub/rsync)(ftp://rsync.samba.org/pub/rsync). |
41059f75 AT |
444 | |
445 | A WEB site is available at | |
9e3c856a | 446 | url(http://rsync.samba.org/)(http://rsync.samba.org/) |
41059f75 AT |
447 | |
448 | We would be delighted to hear from you if you like this program. | |
449 | ||
450 | This program uses the zlib compression library written by Jean-loup | |
451 | Gailly and Mark Adler. | |
452 | ||
453 | manpagesection(THANKS) | |
454 | ||
455 | Thanks to Warren Stanley for his original idea and patch for the rsync | |
456 | server. Thanks to Karsten Thygesen for his many suggestions and | |
457 | documentation! | |
458 | ||
459 | manpageauthor() | |
460 | ||
461 | rsync was written by Andrew Tridgell and Paul Mackerras. They may be | |
9e3c856a | 462 | contacted via email at tridge@samba.org and |
41059f75 AT |
463 | Paul.Mackerras@cs.anu.edu.au |
464 |