1 mailto(rsync-bugs@samba.anu.edu.au)
2 manpage(rsyncd.conf)(5)(13 May 1998)()()
3 manpagename(rsyncd.conf)(configuration file for rsync server)
10 The rsyncd.conf file is the runtime configuration file for rsync when
11 run with the --daemon option. When run in this way rsync becomes a
12 rsync server listening on TCP port 873. Connections from rsync clients
13 are accepted for either anonymous or authenticated rsync sessions.
15 The rsyncd.conf file controls authentication, access, logging and
18 manpagesection(FILE FORMAT)
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'.
24 The file is line-based - that is, each newline-terminated line represents
25 either a comment, a module name or a parameter.
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.
33 Any line beginning with a hash (#) is ignored, as are lines containing
36 Any line ending in a \ is "continued" on the next line in the
37 customary UNIX fashion.
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
44 manpagesection(LAUNCHING THE RSYNC DAEMON)
46 The rsync daemon is launched by specifying the --daemon option to
47 rsync. The daemon must run with root privileges.
49 You can launch it either via inetd or as a standalone daemon. If run
50 as a daemon then just run the command "rsync --daemon" from a suitable
53 When run via inetd you should add a line like this to /etc/services:
57 and a single line something like this to /etc/inetd.conf:
59 quote(rsync stream tcp nowait root /usr/bin/rsync rsyncd --daemon)
61 You will then need to send inetd a HUP signal to tell it to reread its
64 Note that you should not send the rsync server a HUP signal to force
65 it to reread the tt(/etc/rsyncd.conf). The file is re-read on each client
68 manpagesection(GLOBAL OPTIONS)
70 The first parameters in the file (before a [module] header) are the
73 You may also include any module parameters in the global part of the
74 config file in which case the supplied value will override the
75 default for that parameter.
78 dit(bf(motd file)) The "motd file" option allows you to specify a
79 "message of the day" to display to clients on each connect. This
80 usually contains site information and any legal notices. The default
83 dit(bf(max connections)) The "max connections" option allows you to
84 specify the maximum number of simultaneous connections you will allow
85 to your rsync server. Any clients connecting when the maximum has
86 been reached will receive a message telling them to try later.
87 The default is 0 which means no limit.
89 dit(bf(lock file)) The "lock file" option specifies the file to use to
90 support the "max connections" option. The rsync server uses record
91 locking on this file to ensure that the max connections limit is not
92 exceeded. The default is tt(/var/run/rsyncd.lock).
94 dit(bf(log file)) The "log file" option tells the rsync daemon to log
95 messages to that file rather than using syslog. This is particularly
96 useful on systems (such as AIX) where syslog() doesn't work for
99 dit(bf(pid file)) The "pid file" option tells the rsync daemon to write
100 its process id to that file.
102 dit(bf(syslog facility)) The "syslog facility" option allows you to
103 specify the syslog facility name to use when logging messages from the
104 rsync server. You may use any standard syslog facility name which is
105 defined on your system. Common names are auth, authpriv, cron, daemon,
106 ftp, kern, lpr, mail, news, security, syslog, user, uucp, local0,
107 local1, local2, local3, local4, local5, local6 and local7. The default
110 dit(bf(transfer file)) The "transfer logging" option enables per-file
111 logging of downloads and uploads in a format somewhat similar to that
112 used by ftp daemons. If you want to customise the log formats look at
113 log_send, log_recv and log_transfer in log.c
115 dit(bf(socket options)) This option can provide endless fun for people
116 who like to tune their systems to the utmost degree. You can set all
117 sorts of socket options which may make transfers faster (or
118 slower!). Read the man page for the setsockopt() system call for
119 details on some of the options you may be able to set. By default no
120 special socket options are set.
125 manpagesection(MODULE OPTIONS)
127 After the global options you should define a number of modules, each
128 module exports a directory tree as a symbolic name. Modules are
129 exported by specifying a module name in square brackets [module]
130 followed by the options for that module.
134 dit(bf(comment)) The "comment" option specifies a description string
135 that is displayed next to the module name when clients obtain a list
136 of available modules. The default is no comment.
138 dit(bf(path)) The "path" option specifies the directory in the servers
139 filesystem to make available in this module. You must specify this option
140 for each module in tt(/etc/rsyncd.conf).
142 dit(bf(use chroot)) If "use chroot" is true, the rsync server will chroot
143 to the "path" before starting the file transfer with the client. This has
144 the advantage of extra protection against possible implementation security
145 holes, but it has the disadvantages of requiring super-user privileges and
146 of not being able to follow symbolic links outside of the new root path.
147 The default is to use chroot.
149 dit(bf(read only)) The "read only" option determines whether clients
150 will be able to upload files or not. If "read only" is true then any
151 attempted uploads will fail. If "read only" is false then uploads will
152 be possible if file permissions on the server allow them. The default
153 is for all modules to be read only.
155 dit(bf(list)) The "list" option determines if this module should be
156 listed when the client asks for a listing of available modules. By
157 setting this to false you can create hidden modules. The default is
158 for modules to be listable.
160 dit(bf(uid)) The "uid" option specifies the user name or user id that
161 file transfers to and from that module should take place as. In
162 combination with the "gid" option this determines what file
163 permissions are available. The default is the user "nobody".
165 dit(bf(gid)) The "gid" option specifies the group name or group id that
166 file transfers to and from that module should take place as. This
167 complements the "uid" option. The default is the group "nobody".
169 dit(bf(exclude)) The "exclude" option allows you to specify a space
170 separated list of patterns to add to the exclude list. This is
171 equivalent to the client specifying these patterns with the --exclude
172 option. Note that this option is not designed with strong security in
173 mind, it is quite possible that a client may find a way to bypass this
174 exclude list. If you want to absolutely ensure that certain files
175 cannot be accessed then use the uid/gid options in combination with
178 dit(bf(exclude from)) The "exclude from" option specifies a filename
179 on the server that contains exclude patterns, one per line. This is
180 equivalent to the client specifying the --exclude-from option with a
181 equivalent file. See also the note about security for the exclude
184 dit(bf(auth users)) The "auth users" option specifies a comma
185 and space separated list of usernames that will be allowed to connect
186 to this module. The usernames do not need to exist on the local
187 system. If "auth users" is set then the client will be challenged to
188 supply a username and password to connect to the module. A challenge
189 response authentication protocol is used for this exchange. The plain
190 text usernames are passwords are stored in the file specified by the
191 "secrets file" option. The default is for all users to be able to
192 connect without a password (this is called "anonymous rsync").
194 dit(bf(secrets file)) The "secrets file" option specifies the name of
195 a file that contains the username:password pairs used for
196 authenticating this module. This file is only consulted if the "auth
197 users" option is specified. The file is line based and contains
198 username:password pairs separated by a single colon. Any line starting
199 with a hash (#) is considered a comment and is skipped. The passwords
200 can contain any characters but be warned that many operating systems
201 limit the length of passwords that can be typed at the client end, so
202 you may find that passwords longer than 8 characters don't work.
204 bf(You should make sure that the secrets file is not readable by anyone
205 other than the system administrator.) There is no default for the
206 "secrets file" option, you must choose a name (such as
207 tt(/etc/rsyncd.secrets)).
209 dit(bf(hosts allow)) The "hosts allow" option allows you to specify a
210 list of patterns that are matched against a connecting clients
211 hostname and IP address. If none of the patterns match then the
212 connection is rejected.
214 Each pattern can be in one of five forms:
217 it() a dotted decimal IP address. In this case the incoming machines
218 IP address must match exactly.
220 it() a address/mask in the form a.b.c.d/n were n is the number of
221 one bits in in the netmask. All IP addresses which match the masked
222 IP address will be allowed in.
224 it() a address/mask in the form a.b.c.d/e.f.g.h where e.f.g.h is a
225 netmask in dotted decimal notation. All IP addresses which match the masked
226 IP address will be allowed in.
228 it() a hostname. The hostname as determined by a reverse lookup will
229 be matched (case insensitive) against the pattern. Only an exact
232 it() a hostname pattern using wildcards. These are matched using the
233 same rules as normal unix filename matching. If the pattern matches
234 then the client is allowed in.
237 You can also combine "hosts allow" with a separate "hosts deny"
238 option. If both options are specified then the "hosts allow" option s
239 checked first and a match results in the client being able to
240 connect. The "hosts deny" option is then checked and a match means
241 that the host is rejected. If the host does not match either the
242 "hosts allow" or the "hosts deny" patterns then it is allowed to
245 The default is no "hosts allow" option, which means all hosts can connect.
247 dit(bf(hosts deny)) The "hosts deny" option allows you to specify a
248 list of patterns that are matched against a connecting clients
249 hostname and IP address. If the pattern matches then the connection is
250 rejected. See the "hosts allow" option for more information.
252 The default is no "hosts deny" option, which means all hosts can connect.
256 manpagesection(AUTHENTICATION STRENGTH)
258 The authentication protocol used in rsync is a 128 bit MD4 based
259 challenge response system. Although I believe that no one has ever
260 demonstrated a brute-force break of this sort of system you should
261 realise that this is not a "military strength" authentication system.
262 It should be good enough for most purposes but if you want really top
263 quality security then I recommend that you run rsync over ssh.
265 Also note that the rsync server protocol does not currently provide any
266 encryption of the data that is transferred over the link. Only
267 authentication is provided. Use ssh as the transport if you want
270 Future versions of rsync may support SSL for better authentication and
271 encryption, but that is still being investigated.
273 manpagesection(EXAMPLES)
275 A simple rsyncd.conf file that allow anonymous rsync to a ftp area at
276 tt(/home/ftp) would be:
281 comment = ftp export area
285 A more sophisticated example would be:
290 max connections = 4 nl()
291 syslog facility = local5 nl()
292 pid file = /etc/rsyncd.pid
296 comment = whole ftp area (approx 6.1 GB)
299 path = /var/ftp/pub/samba
300 comment = Samba ftp area (approx 300 MB)
303 path = /var/ftp/pub/rsync
304 comment = rsync ftp area (approx 6 MB)
307 path = /public_html/samba
308 comment = Samba WWW pages (approx 240 MB)
312 comment = CVS repository (requires authentication)
313 auth users = tridge, susan
314 secrets file = /etc/rsyncd.secrets
317 The /etc/rsyncd.secrets file would look something like this:
334 The rsync server does not send all types of error messages to the
335 client. this means a client may be mystified as to why a transfer
336 failed. The error will have been logged by syslog on the server.
338 Please report bugs! The rsync bug tracking system is online at
339 url(http://samba.anu.edu.au/rsync/)(http://samba.anu.edu.au/rsync/)
341 manpagesection(VERSION)
342 This man page is current for version 2.0 of rsync
344 manpagesection(CREDITS)
346 rsync is distributed under the GNU public license. See the file
349 The primary ftp site for rsync is
350 url(ftp://samba.anu.edu.au/pub/rsync)(ftp://samba.anu.edu.au/pub/rsync).
352 A WEB site is available at
353 url(http://samba.anu.edu.au/rsync/)(http://samba.anu.edu.au/rsync/)
355 We would be delighted to hear from you if you like this program.
357 This program uses the zlib compression library written by Jean-loup
358 Gailly and Mark Adler.
360 manpagesection(THANKS)
362 Thanks to Warren Stanley for his original idea and patch for the rsync
363 server. Thanks to Karsten Thygesen for his many suggestions and
368 rsync was written by Andrew Tridgell and Paul Mackerras. They may be
369 contacted via email at tridge@samba.anu.edu.au and
370 Paul.Mackerras@cs.anu.edu.au