Commit | Line | Data |
---|---|---|
9e3c856a | 1 | mailto(rsync-bugs@samba.org) |
c8d771a0 | 2 | manpage(rsyncd.conf)(5)(30 Apr 2004)()() |
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 | |
04657e42 | 11 | run as an rsync server. |
41059f75 AT |
12 | |
13 | The rsyncd.conf file controls authentication, access, logging and | |
14 | available modules. | |
15 | ||
16 | manpagesection(FILE FORMAT) | |
17 | ||
18 | The file consists of modules and parameters. A module begins with the | |
19 | name of the module in square brackets and continues until the next | |
20 | module begins. Modules contain parameters of the form 'name = value'. | |
21 | ||
22 | The file is line-based - that is, each newline-terminated line represents | |
23 | either a comment, a module name or a parameter. | |
24 | ||
25 | Only the first equals sign in a parameter is significant. Whitespace before | |
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 | ||
31 | Any line beginning with a hash (#) is ignored, as are lines containing | |
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 | |
40 | in string values. | |
41 | ||
5315b793 | 42 | manpagesection(LAUNCHING THE RSYNC DAEMON) |
41059f75 AT |
43 | |
44 | The rsync daemon is launched by specifying the --daemon option to | |
f5c20813 MP |
45 | rsync. |
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 | |
54 | just run the command "rsync --daemon" from a suitable startup script. | |
55 | If run from an rsync client via a remote shell (by specifying both the | |
56 | "-e/--rsh" option and server mode with "::" or "rsync://"), the --daemon | |
57 | option is automatically passed to the remote side. | |
41059f75 AT |
58 | |
59 | When run via inetd you should add a line like this to /etc/services: | |
60 | ||
e22de162 | 61 | quote(rsync 873/tcp) |
41059f75 | 62 | |
e22de162 | 63 | and a single line something like this to /etc/inetd.conf: |
41059f75 | 64 | |
e22de162 | 65 | quote(rsync stream tcp nowait root /usr/bin/rsync rsyncd --daemon) |
41059f75 | 66 | |
79f118d8 DD |
67 | Replace "/usr/bin/rsync" with the path to where you have rsync installed on |
68 | your system. You will then need to send inetd a HUP signal to tell it to | |
69 | reread its config file. | |
41059f75 AT |
70 | |
71 | Note that you should not send the rsync server a HUP signal to force | |
30e8c8e1 | 72 | it to reread the tt(rsyncd.conf) file. The file is re-read on each client |
41059f75 AT |
73 | connection. |
74 | ||
75 | manpagesection(GLOBAL OPTIONS) | |
76 | ||
77 | The first parameters in the file (before a [module] header) are the | |
78 | global parameters. | |
79 | ||
80 | You may also include any module parameters in the global part of the | |
81 | config file in which case the supplied value will override the | |
82 | default for that parameter. | |
83 | ||
84 | startdit() | |
85 | dit(bf(motd file)) The "motd file" option allows you to specify a | |
5315b793 | 86 | "message of the day" to display to clients on each connect. This |
41059f75 AT |
87 | usually contains site information and any legal notices. The default |
88 | is no motd file. | |
89 | ||
37863201 AT |
90 | dit(bf(log file)) The "log file" option tells the rsync daemon to log |
91 | messages to that file rather than using syslog. This is particularly | |
92 | useful on systems (such as AIX) where syslog() doesn't work for | |
8638dd48 DD |
93 | chrooted programs. |
94 | ||
95 | dit(bf(pid file)) The "pid file" option tells the rsync daemon to write | |
58811a0a | 96 | its process ID to that file. |
37863201 | 97 | |
41059f75 AT |
98 | dit(bf(syslog facility)) The "syslog facility" option allows you to |
99 | specify the syslog facility name to use when logging messages from the | |
100 | rsync server. You may use any standard syslog facility name which is | |
101 | defined on your system. Common names are auth, authpriv, cron, daemon, | |
102 | ftp, kern, lpr, mail, news, security, syslog, user, uucp, local0, | |
103 | local1, local2, local3, local4, local5, local6 and local7. The default | |
104 | is daemon. | |
105 | ||
a6801c39 AT |
106 | dit(bf(socket options)) This option can provide endless fun for people |
107 | who like to tune their systems to the utmost degree. You can set all | |
108 | sorts of socket options which may make transfers faster (or | |
109 | slower!). Read the man page for the setsockopt() system call for | |
110 | details on some of the options you may be able to set. By default no | |
111 | special socket options are set. | |
112 | ||
41059f75 AT |
113 | enddit() |
114 | ||
115 | ||
116 | manpagesection(MODULE OPTIONS) | |
117 | ||
118 | After the global options you should define a number of modules, each | |
119 | module exports a directory tree as a symbolic name. Modules are | |
120 | exported by specifying a module name in square brackets [module] | |
121 | followed by the options for that module. | |
122 | ||
123 | startdit() | |
124 | ||
125 | dit(bf(comment)) The "comment" option specifies a description string | |
126 | that is displayed next to the module name when clients obtain a list | |
127 | of available modules. The default is no comment. | |
128 | ||
129 | dit(bf(path)) The "path" option specifies the directory in the servers | |
8638dd48 | 130 | filesystem to make available in this module. You must specify this option |
30e8c8e1 | 131 | for each module in tt(rsyncd.conf). |
8638dd48 DD |
132 | |
133 | dit(bf(use chroot)) If "use chroot" is true, the rsync server will chroot | |
134 | to the "path" before starting the file transfer with the client. This has | |
135 | the advantage of extra protection against possible implementation security | |
fca9a9b0 | 136 | holes, but it has the disadvantages of requiring super-user privileges, |
5f7ce204 | 137 | of not being able to follow symbolic links outside of the new root path |
fa8c787d | 138 | when reading, and of complicating the preservation of usernames and groups |
cb290916 | 139 | (see below). When "use chroot" is false, for security reasons, |
fca9a9b0 | 140 | symlinks may only be relative paths pointing to other files within the root |
5dc6e9c9 WD |
141 | path, and leading slashes are removed from most absolute paths (options |
142 | such as --backup-dir, --compare-dest, etc. interpret an absolute path as | |
143 | rooted in the module's "path" dir, just as if chroot was specified). | |
144 | The default for "use chroot" is true. | |
41059f75 | 145 | |
cb290916 | 146 | In order to preserve usernames and groupnames, rsync needs to be able to |
d99b4ccf WD |
147 | use the standard library functions for looking up names and IDs (i.e. |
148 | getpwuid(), getgrgid(), getpwname(), and getgrnam()). This means a | |
149 | process in the chroot namespace will need to have access to the resources | |
150 | used by these library functions (traditionally /etc/passwd and | |
151 | /etc/group). If these resources are not available, rsync will only be | |
152 | able to copy the IDs, just as if the --numeric-ids option had been | |
153 | specified. | |
154 | ||
155 | Note that you are free to setup user/group information in the chroot area | |
156 | differently from your normal system. For example, you could abbreviate | |
157 | the list of users and groups. Also, you can protect this information | |
158 | from being downloaded by adding an exclude rule to the rsync.conf file | |
159 | (e.g. "exclude = /etc/"). To protect it from being changed by an upload | |
160 | (if the module is not read only), be sure to set the permissions (or | |
161 | owner) on the files and/or parent directories so that they cannot be | |
162 | written by the daemon. | |
cb290916 | 163 | |
5e71c444 | 164 | dit(bf(max connections)) The "max connections" option allows you to |
9ef1cc7c DD |
165 | specify the maximum number of simultaneous connections you will allow. |
166 | Any clients connecting when the maximum has been reached will receive a | |
167 | message telling them to try later. The default is 0 which means no limit. | |
168 | See also the "lock file" option. | |
5e71c444 AT |
169 | |
170 | dit(bf(lock file)) The "lock file" option specifies the file to use to | |
171 | support the "max connections" option. The rsync server uses record | |
172 | locking on this file to ensure that the max connections limit is not | |
9ef1cc7c DD |
173 | exceeded for the modules sharing the lock file. |
174 | The default is tt(/var/run/rsyncd.lock). | |
5e71c444 | 175 | |
41059f75 AT |
176 | dit(bf(read only)) The "read only" option determines whether clients |
177 | will be able to upload files or not. If "read only" is true then any | |
178 | attempted uploads will fail. If "read only" is false then uploads will | |
179 | be possible if file permissions on the server allow them. The default | |
180 | is for all modules to be read only. | |
181 | ||
7a92ded3 WD |
182 | dit(bf(write only)) The "write only" option determines whether clients |
183 | will be able to download files or not. If "write only" is true then any | |
184 | attempted downloads will fail. If "write only" is false then downloads | |
185 | will be possible if file permissions on the server allow them. The | |
186 | default is for this option to be disabled. | |
187 | ||
41059f75 AT |
188 | dit(bf(list)) The "list" option determines if this module should be |
189 | listed when the client asks for a listing of available modules. By | |
190 | setting this to false you can create hidden modules. The default is | |
191 | for modules to be listable. | |
192 | ||
58811a0a | 193 | dit(bf(uid)) The "uid" option specifies the user name or user ID that |
716baed7 DD |
194 | file transfers to and from that module should take place as when the daemon |
195 | was run as root. In combination with the "gid" option this determines what | |
2af27ad9 MP |
196 | file permissions are available. The default is uid -2, which is normally |
197 | the user "nobody". | |
41059f75 | 198 | |
58811a0a | 199 | dit(bf(gid)) The "gid" option specifies the group name or group ID that |
716baed7 | 200 | file transfers to and from that module should take place as when the daemon |
2af27ad9 MP |
201 | was run as root. This complements the "uid" option. The default is gid -2, |
202 | which is normally the group "nobody". | |
41059f75 | 203 | |
8f3a2d54 | 204 | dit(bf(exclude)) The "exclude" option allows you to specify a space |
83fd337d S |
205 | separated list of patterns to add to the exclude list. |
206 | This is only superficially equivalent | |
207 | to the client specifying these patterns with the --exclude option. | |
208 | Only one "exclude" option may be specified, but | |
209 | you can use "-" and "+" before patterns to specify exclude/include. | |
210 | ||
211 | Because this exclude list is not passed to the client it only applies on | |
7c2d381c DD |
212 | the server: that is, it excludes files received by a client when receiving |
213 | from a server and files deleted on a server when sending to a server, but | |
214 | it doesn't exclude files sent from a client when sending to a server or | |
215 | files deleted on a client when receiving from a server. | |
651443a7 DD |
216 | |
217 | Note that this option is not designed with strong security in | |
8f3a2d54 AT |
218 | mind, it is quite possible that a client may find a way to bypass this |
219 | exclude list. If you want to absolutely ensure that certain files | |
220 | cannot be accessed then use the uid/gid options in combination with | |
221 | file permissions. | |
222 | ||
223 | dit(bf(exclude from)) The "exclude from" option specifies a filename | |
83fd337d S |
224 | on the server that contains exclude patterns, one per line. |
225 | This is only superficially equivalent | |
226 | to the client specifying the --exclude-from option with an equivalent file. | |
227 | See the "exclude" option above. | |
8f3a2d54 | 228 | |
cd64343a DD |
229 | dit(bf(include)) The "include" option allows you to specify a space |
230 | separated list of patterns which rsync should not exclude. This is | |
83fd337d S |
231 | only superficially equivalent to the client specifying these patterns |
232 | with the --include option because it applies only on the server. | |
233 | This is useful as it | |
7c2d381c DD |
234 | allows you to build up quite complex exclude/include rules. Only one |
235 | "include" option may be specified, but you can use "+" and "-" before | |
83fd337d | 236 | patterns to switch include/exclude. See the "exclude" option above. |
cd64343a DD |
237 | |
238 | dit(bf(include from)) The "include from" option specifies a filename | |
239 | on the server that contains include patterns, one per line. This is | |
83fd337d S |
240 | only superficially equivalent to the client specifying the |
241 | --include-from option with a equivalent file. | |
242 | See the "exclude" option above. | |
cd64343a | 243 | |
5d78a102 AT |
244 | dit(bf(auth users)) The "auth users" option specifies a comma and |
245 | space separated list of usernames that will be allowed to connect to | |
246 | this module. The usernames do not need to exist on the local | |
247 | system. The usernames may also contain shell wildcard characters. If | |
248 | "auth users" is set then the client will be challenged to supply a | |
249 | username and password to connect to the module. A challenge response | |
250 | authentication protocol is used for this exchange. The plain text | |
251 | usernames are passwords are stored in the file specified by the | |
41059f75 AT |
252 | "secrets file" option. The default is for all users to be able to |
253 | connect without a password (this is called "anonymous rsync"). | |
254 | ||
bef49340 WD |
255 | See also the bf(CONNECTING TO AN RSYNC SERVER OVER A REMOTE SHELL |
256 | PROGRAM) section in rsync(1) for information on how handle an | |
257 | rsyncd.conf-level username that differs from the remote-shell-level | |
58811a0a | 258 | username when using a remote shell to connect to an rsync server. |
bef49340 | 259 | |
41059f75 AT |
260 | dit(bf(secrets file)) The "secrets file" option specifies the name of |
261 | a file that contains the username:password pairs used for | |
262 | authenticating this module. This file is only consulted if the "auth | |
263 | users" option is specified. The file is line based and contains | |
264 | username:password pairs separated by a single colon. Any line starting | |
265 | with a hash (#) is considered a comment and is skipped. The passwords | |
266 | can contain any characters but be warned that many operating systems | |
267 | limit the length of passwords that can be typed at the client end, so | |
268 | you may find that passwords longer than 8 characters don't work. | |
269 | ||
3ca8e68f | 270 | There is no default for the "secrets file" option, you must choose a name |
205c27ac DD |
271 | (such as tt(/etc/rsyncd.secrets)). The file must normally not be readable |
272 | by "other"; see "strict modes". | |
3ca8e68f DD |
273 | |
274 | dit(bf(strict modes)) The "strict modes" option determines whether or not | |
275 | the permissions on the secrets file will be checked. If "strict modes" is | |
58811a0a | 276 | true, then the secrets file must not be readable by any user ID other |
3ca8e68f DD |
277 | than the one that the rsync daemon is running under. If "strict modes" is |
278 | false, the check is not performed. The default is true. This option | |
279 | was added to accommodate rsync running on the Windows operating system. | |
41059f75 AT |
280 | |
281 | dit(bf(hosts allow)) The "hosts allow" option allows you to specify a | |
282 | list of patterns that are matched against a connecting clients | |
283 | hostname and IP address. If none of the patterns match then the | |
284 | connection is rejected. | |
285 | ||
286 | Each pattern can be in one of five forms: | |
287 | ||
288 | itemize( | |
61ca7d59 DD |
289 | it() a dotted decimal IPv4 address of the form a.b.c.d, or an IPv6 address |
290 | of the form a:b:c::d:e:f. In this case the incoming machine's IP address | |
bc2b4963 DD |
291 | must match exactly. |
292 | ||
61ca7d59 DD |
293 | it() an address/mask in the form ipaddr/n where ipaddr is the IP address |
294 | and n is the number of one bits in the netmask. All IP addresses which | |
295 | match the masked IP address will be allowed in. | |
bc2b4963 | 296 | |
61ca7d59 DD |
297 | it() an address/mask in the form ipaddr/maskaddr where ipaddr is the |
298 | IP address and maskaddr is the netmask in dotted decimal notation for IPv4, | |
299 | or similar for IPv6, e.g. ffff:ffff:ffff:ffff:: instead of /64. All IP | |
300 | addresses which match the masked IP address will be allowed in. | |
41059f75 AT |
301 | |
302 | it() a hostname. The hostname as determined by a reverse lookup will | |
5315b793 | 303 | be matched (case insensitive) against the pattern. Only an exact |
41059f75 AT |
304 | match is allowed in. |
305 | ||
306 | it() a hostname pattern using wildcards. These are matched using the | |
307 | same rules as normal unix filename matching. If the pattern matches | |
5315b793 | 308 | then the client is allowed in. |
41059f75 AT |
309 | ) |
310 | ||
61ca7d59 DD |
311 | Note IPv6 link-local addresses can have a scope in the address specification: |
312 | ||
313 | quote(fe80::1%link1) | |
314 | quote(fe80::%link1/64) | |
315 | quote(fe80::%link1/ffff:ffff:ffff:ffff::) | |
316 | ||
41059f75 AT |
317 | You can also combine "hosts allow" with a separate "hosts deny" |
318 | option. If both options are specified then the "hosts allow" option s | |
5315b793 | 319 | checked first and a match results in the client being able to |
41059f75 AT |
320 | connect. The "hosts deny" option is then checked and a match means |
321 | that the host is rejected. If the host does not match either the | |
322 | "hosts allow" or the "hosts deny" patterns then it is allowed to | |
323 | connect. | |
324 | ||
325 | The default is no "hosts allow" option, which means all hosts can connect. | |
326 | ||
de2fd20e | 327 | dit(bf(hosts deny)) The "hosts deny" option allows you to specify a |
41059f75 AT |
328 | list of patterns that are matched against a connecting clients |
329 | hostname and IP address. If the pattern matches then the connection is | |
330 | rejected. See the "hosts allow" option for more information. | |
331 | ||
332 | The default is no "hosts deny" option, which means all hosts can connect. | |
333 | ||
cda2ae84 | 334 | dit(bf(ignore errors)) The "ignore errors" option tells rsyncd to |
58811a0a | 335 | ignore I/O errors on the server when deciding whether to run the delete |
cda2ae84 | 336 | phase of the transfer. Normally rsync skips the --delete step if any |
58811a0a WD |
337 | I/O errors have occurred in order to prevent disasterous deletion due |
338 | to a temporary resource shortage or other I/O error. In some cases this | |
cda2ae84 AT |
339 | test is counter productive so you can use this option to turn off this |
340 | behaviour. | |
341 | ||
78043d19 AT |
342 | dit(bf(ignore nonreadable)) This tells the rsync server to completely |
343 | ignore files that are not readable by the user. This is useful for | |
344 | public archives that may have some non-readable files among the | |
345 | directories, and the sysadmin doesn't want those files to be seen at all. | |
346 | ||
81791cfc AT |
347 | dit(bf(transfer logging)) The "transfer logging" option enables per-file |
348 | logging of downloads and uploads in a format somewhat similar to that | |
14d43f1f | 349 | used by ftp daemons. If you want to customize the log formats look at |
81791cfc AT |
350 | the log format option. |
351 | ||
352 | dit(bf(log format)) The "log format" option allows you to specify the | |
353 | format used for logging file transfers when transfer logging is | |
354 | enabled. The format is a text string containing embedded single | |
355 | character escape sequences prefixed with a percent (%) character. | |
356 | ||
357 | The prefixes that are understood are: | |
358 | ||
359 | itemize( | |
360 | it() %h for the remote host name | |
361 | it() %a for the remote IP address | |
362 | it() %l for the length of the file in bytes | |
58811a0a | 363 | it() %p for the process ID of this rsync session |
81791cfc AT |
364 | it() %o for the operation, which is either "send" or "recv" |
365 | it() %f for the filename | |
366 | it() %P for the module path | |
367 | it() %m for the module name | |
b882b497 | 368 | it() %t for the current date time |
81791cfc AT |
369 | it() %u for the authenticated username (or the null string) |
370 | it() %b for the number of bytes actually transferred | |
371 | it() %c when sending files this gives the number of checksum bytes | |
372 | received for this file | |
373 | ) | |
374 | ||
b882b497 DD |
375 | The default log format is "%o %h [%a] %m (%u) %f %l", and a "%t [%p] " |
376 | is always added to the beginning when using the "log file" option. | |
81791cfc | 377 | |
14d43f1f | 378 | A perl script called rsyncstats to summarize this format is included |
81791cfc AT |
379 | in the rsync source code distribution. |
380 | ||
381 | dit(bf(timeout)) The "timeout" option allows you to override the | |
58811a0a | 382 | clients choice for I/O timeout for this module. Using this option you |
81791cfc AT |
383 | can ensure that rsync won't wait on a dead client forever. The timeout |
384 | is specified in seconds. A value of zero means no timeout and is the | |
385 | default. A good choice for anonymous rsync servers may be 600 (giving | |
386 | a 10 minute timeout). | |
387 | ||
cd8185f2 AT |
388 | dit(bf(refuse options)) The "refuse options" option allows you to |
389 | specify a space separated list of rsync command line options that will | |
63f0774f DD |
390 | be refused by your rsync server. The full names of the options must be |
391 | used (i.e., you must use "checksum" not "c" to disable checksumming). | |
392 | When an option is refused, the server prints an error message and exits. | |
393 | To prevent all compression, you can use "dont compress = *" (see below) | |
394 | instead of "refuse options = compress" to avoid returning an error to a | |
395 | client that requests compression. | |
cd8185f2 | 396 | |
83fff1aa AT |
397 | dit(bf(dont compress)) The "dont compress" option allows you to select |
398 | filenames based on wildcard patterns that should not be compressed | |
399 | during transfer. Compression is expensive in terms of CPU usage so it | |
400 | is usually good to not try to compress files that won't compress well, | |
401 | such as already compressed files. | |
402 | ||
403 | The "dont compress" option takes a space separated list of | |
404 | case-insensitive wildcard patterns. Any source filename matching one | |
405 | of the patterns will not be compressed during transfer. | |
406 | ||
69c65227 | 407 | The default setting is verb(*.gz *.tgz *.zip *.z *.rpm *.deb *.iso *.bz2 *.tbz) |
83fff1aa | 408 | |
41059f75 AT |
409 | enddit() |
410 | ||
4c3d16be AT |
411 | manpagesection(AUTHENTICATION STRENGTH) |
412 | ||
413 | The authentication protocol used in rsync is a 128 bit MD4 based | |
414 | challenge response system. Although I believe that no one has ever | |
415 | demonstrated a brute-force break of this sort of system you should | |
14d43f1f | 416 | realize that this is not a "military strength" authentication system. |
4c3d16be AT |
417 | It should be good enough for most purposes but if you want really top |
418 | quality security then I recommend that you run rsync over ssh. | |
419 | ||
420 | Also note that the rsync server protocol does not currently provide any | |
f39281ae | 421 | encryption of the data that is transferred over the connection. Only |
4c3d16be AT |
422 | authentication is provided. Use ssh as the transport if you want |
423 | encryption. | |
424 | ||
425 | Future versions of rsync may support SSL for better authentication and | |
426 | encryption, but that is still being investigated. | |
427 | ||
e6f9e388 WD |
428 | manpagesection(RUNNING AN RSYNC SERVER OVER A REMOTE SHELL PROGRAM) |
429 | ||
430 | If rsync is run with both the --daemon and --rsh (-e) options, it will | |
431 | spawn an rsync daemon using a remote shell connection. Several | |
432 | configuration options will not be available unless the remote user is | |
433 | root (e.g. chroot, setuid/setgid, etc.). There is no need to configure | |
434 | inetd or the services map to include the rsync server port if you run an | |
435 | rsync server only via a remote shell program. | |
436 | ||
437 | ADVANCED: To run an rsync server out of a single-use ssh key, use the | |
438 | "command=em(COMMAND)" syntax in the remote user's authorized_keys entry, | |
439 | where command would be | |
440 | ||
441 | quote(rsync --server --daemon .) | |
442 | ||
443 | NOTE: rsync's argument parsing expects the trailing ".", so make sure | |
58811a0a | 444 | that it's there. If you want to use an rsyncd.conf(5)-style |
e6f9e388 WD |
445 | configuration file other than the default, you can added a |
446 | --config option to the em(command): | |
447 | ||
448 | quote(rsync --server --daemon --config=em(file) .) | |
449 | ||
450 | Note that the "--server" here is the internal option that rsync uses to | |
451 | run the remote version of rsync that it communicates with, and thus you | |
452 | should not be using the --server option under normal circumstances. | |
453 | ||
41059f75 AT |
454 | manpagesection(EXAMPLES) |
455 | ||
456 | A simple rsyncd.conf file that allow anonymous rsync to a ftp area at | |
e22de162 | 457 | tt(/home/ftp) would be: |
41059f75 AT |
458 | |
459 | verb( | |
460 | [ftp] | |
e22de162 AT |
461 | path = /home/ftp |
462 | comment = ftp export area | |
41059f75 AT |
463 | ) |
464 | ||
465 | ||
466 | A more sophisticated example would be: | |
467 | ||
e22de162 AT |
468 | uid = nobody nl() |
469 | gid = nobody nl() | |
8638dd48 | 470 | use chroot = no nl() |
e22de162 AT |
471 | max connections = 4 nl() |
472 | syslog facility = local5 nl() | |
0f621785 | 473 | pid file = /var/run/rsyncd.pid |
41059f75 | 474 | |
e22de162 | 475 | verb([ftp] |
41059f75 AT |
476 | path = /var/ftp/pub |
477 | comment = whole ftp area (approx 6.1 GB) | |
478 | ||
479 | [sambaftp] | |
480 | path = /var/ftp/pub/samba | |
481 | comment = Samba ftp area (approx 300 MB) | |
482 | ||
483 | [rsyncftp] | |
484 | path = /var/ftp/pub/rsync | |
485 | comment = rsync ftp area (approx 6 MB) | |
486 | ||
487 | [sambawww] | |
488 | path = /public_html/samba | |
489 | comment = Samba WWW pages (approx 240 MB) | |
490 | ||
491 | [cvs] | |
492 | path = /data/cvs | |
493 | comment = CVS repository (requires authentication) | |
494 | auth users = tridge, susan | |
495 | secrets file = /etc/rsyncd.secrets | |
496 | ) | |
497 | ||
498 | The /etc/rsyncd.secrets file would look something like this: | |
499 | ||
e22de162 | 500 | tridge:mypass nl() |
41059f75 | 501 | susan:herpass |
41059f75 AT |
502 | |
503 | manpagefiles() | |
504 | ||
30e8c8e1 | 505 | /etc/rsyncd.conf or rsyncd.conf |
41059f75 AT |
506 | |
507 | manpageseealso() | |
508 | ||
509 | rsync(1) | |
510 | ||
511 | manpagediagnostics() | |
512 | ||
513 | manpagebugs() | |
514 | ||
515 | The rsync server does not send all types of error messages to the | |
516 | client. this means a client may be mystified as to why a transfer | |
517 | failed. The error will have been logged by syslog on the server. | |
518 | ||
519 | Please report bugs! The rsync bug tracking system is online at | |
9e3c856a | 520 | url(http://rsync.samba.org/)(http://rsync.samba.org/) |
41059f75 AT |
521 | |
522 | manpagesection(VERSION) | |
c53217a2 | 523 | This man page is current for version 2.x of rsync. |
41059f75 AT |
524 | |
525 | manpagesection(CREDITS) | |
526 | ||
527 | rsync is distributed under the GNU public license. See the file | |
528 | COPYING for details. | |
529 | ||
530 | The primary ftp site for rsync is | |
9e3c856a | 531 | url(ftp://rsync.samba.org/pub/rsync)(ftp://rsync.samba.org/pub/rsync). |
41059f75 AT |
532 | |
533 | A WEB site is available at | |
9e3c856a | 534 | url(http://rsync.samba.org/)(http://rsync.samba.org/) |
41059f75 AT |
535 | |
536 | We would be delighted to hear from you if you like this program. | |
537 | ||
538 | This program uses the zlib compression library written by Jean-loup | |
539 | Gailly and Mark Adler. | |
540 | ||
541 | manpagesection(THANKS) | |
542 | ||
543 | Thanks to Warren Stanley for his original idea and patch for the rsync | |
544 | server. Thanks to Karsten Thygesen for his many suggestions and | |
545 | documentation! | |
546 | ||
547 | manpageauthor() | |
548 | ||
549 | rsync was written by Andrew Tridgell and Paul Mackerras. They may be | |
9e3c856a | 550 | contacted via email at tridge@samba.org and |
41059f75 AT |
551 | Paul.Mackerras@cs.anu.edu.au |
552 |