preparing for release of 2.0.0
[rsync/rsync.git] / rsyncd.conf.yo
CommitLineData
41059f75
AT
1mailto(rsync-bugs@samba.anu.edu.au)
2manpage(rsyncd.conf)(5)(13 May 1998)()()
3manpagename(rsyncd.conf)(configuration file for rsync server)
4manpagesynopsis()
5
6rsyncd.conf
7
8manpagedescription()
9
10The rsyncd.conf file is the runtime configuration file for rsync when
11run with the -daemon option. When run in this way rsync becomes a
12rsync server listening on TCP port 873. Connections from rsync clients
13are accepted for either anonymous or authenticated rsync sessions.
14
15The rsyncd.conf file controls authentication, access, logging and
16available modules.
17
18manpagesection(FILE FORMAT)
19
20The file consists of modules and parameters. A module begins with the
21name of the module in square brackets and continues until the next
22module begins. Modules contain parameters of the form 'name = value'.
23
24The file is line-based - that is, each newline-terminated line represents
25either a comment, a module name or a parameter.
26
27Only the first equals sign in a parameter is significant. Whitespace before
28or after the first equals sign is discarded. Leading, trailing and internal
29whitespace in module and parameter names is irrelevant. Leading and
30trailing whitespace in a parameter value is discarded. Internal whitespace
31within a parameter value is retained verbatim.
32
33Any line beginning with a hash (#) is ignored, as are lines containing
34only whitespace.
35
36Any line ending in a \e is "continued" on the next line in the
37customary UNIX fashion.
38
39The 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
41true/false. Case is not significant in boolean values, but is preserved
42in string values.
43
5315b793 44manpagesection(LAUNCHING THE RSYNC DAEMON)
41059f75
AT
45
46The rsync daemon is launched by specifying the --daemon option to
5315b793 47rsync. The daemon must run with root privileges.
41059f75
AT
48
49You can launch it either via inetd or as a standalone daemon. If run
50as a daemon then just run the command "rsync -daemon" from a suitable
51startup script.
52
53When run via inetd you should add a line like this to /etc/services:
54
55 rsync 873/tcp
56
57and a line something like this to /etc/inetd.conf:
58
59 rsync stream tcp nowait root /usr/bin/rsync rsyncd --daemon
60
61You will then need to send inetd a HUP signal to tell it to reread its
62config file.
63
64Note that you should not send the rsync server a HUP signal to force
65it to reread the /etc/rsyncd.conf. The file is re-read on each client
66connection.
67
68manpagesection(GLOBAL OPTIONS)
69
70The first parameters in the file (before a [module] header) are the
71global parameters.
72
73You may also include any module parameters in the global part of the
74config file in which case the supplied value will override the
75default for that parameter.
76
77startdit()
78dit(bf(motd file)) The "motd file" option allows you to specify a
5315b793 79"message of the day" to display to clients on each connect. This
41059f75
AT
80usually contains site information and any legal notices. The default
81is no motd file.
82
83dit(bf(max connections)) The "max connections" option allows you to
84specify the maximum number of simultaneous connections you will allow
85to your rsync server. Any clients connecting when the maximum has
86been reached will receive a message telling them to try later.
87The default is 0 which means no limit.
88
89dit(bf(lock file)) The "lock file" option specifies the file to use to
90support the "max connections" option. The rsync server uses record
91locking on this file to ensure that the max connections limit is not
92exceeded. The default is /var/run/rsyncd.lock
93
94dit(bf(syslog facility)) The "syslog facility" option allows you to
95specify the syslog facility name to use when logging messages from the
96rsync server. You may use any standard syslog facility name which is
97defined on your system. Common names are auth, authpriv, cron, daemon,
98ftp, kern, lpr, mail, news, security, syslog, user, uucp, local0,
99local1, local2, local3, local4, local5, local6 and local7. The default
100is daemon.
101
102enddit()
103
104
105manpagesection(MODULE OPTIONS)
106
107After the global options you should define a number of modules, each
108module exports a directory tree as a symbolic name. Modules are
109exported by specifying a module name in square brackets [module]
110followed by the options for that module.
111
112startdit()
113
114dit(bf(comment)) The "comment" option specifies a description string
115that is displayed next to the module name when clients obtain a list
116of available modules. The default is no comment.
117
118dit(bf(path)) The "path" option specifies the directory in the servers
119filesystem to make available in this module. The rsync server will
120chroot to this path before starting the file transfer with the
121client. You must specify this option for each module in /etc/rsyncd.conf.
122
123dit(bf(read only)) The "read only" option determines whether clients
124will be able to upload files or not. If "read only" is true then any
125attempted uploads will fail. If "read only" is false then uploads will
126be possible if file permissions on the server allow them. The default
127is for all modules to be read only.
128
129dit(bf(list)) The "list" option determines if this module should be
130listed when the client asks for a listing of available modules. By
131setting this to false you can create hidden modules. The default is
132for modules to be listable.
133
134dit(bf(uid)) The "uid" option specifies the user name or user id that
135file transfers to and from that module should take place as. In
136combination with the "gid" option this determines what file
137permissions are available. The default is the user "nobody".
138
139dit(bf(gid)) The "gid" option specifies the group name or group id that
140file transfers to and from that module should take place as. This
141complements the "uid" option. The default is the group "nobody".
142
143dit(bf(auth users)) The "auth users" option specifies a comma
144and space separated list of usernames that will be allowed to connect
145to this module. The usernames do not need to exist on the local
146system. If "auth users" is set then the client will be challenged to
147supply a username and password to connect to the module. A challenge
148response authentication protocol is used for this exchange. The plain
149text usernames are passwords are stored in the file specified by the
150"secrets file" option. The default is for all users to be able to
151connect without a password (this is called "anonymous rsync").
152
153dit(bf(secrets file)) The "secrets file" option specifies the name of
154a file that contains the username:password pairs used for
155authenticating this module. This file is only consulted if the "auth
156users" option is specified. The file is line based and contains
157username:password pairs separated by a single colon. Any line starting
158with a hash (#) is considered a comment and is skipped. The passwords
159can contain any characters but be warned that many operating systems
160limit the length of passwords that can be typed at the client end, so
161you may find that passwords longer than 8 characters don't work.
162
163bf(You should make sure that the secrets file is not readable by anyone
164other than the system administrator.) There is no default for the
165"secrets file" option, you must choose a name (such as
166/etc/rsyncd.secrets).
167
168dit(bf(hosts allow)) The "hosts allow" option allows you to specify a
169list of patterns that are matched against a connecting clients
170hostname and IP address. If none of the patterns match then the
171connection is rejected.
172
173Each pattern can be in one of five forms:
174
175itemize(
176 it() a dotted decimal IP address. In this case the incoming machines
177 IP address must match exactly.
178
179 it() a address/mask in the form a.b.c.d/n were n is the number of
180 one bits in in the netmask. All IP addresses which match the masked
181 IP address will be allowed in.
182
183 it() a address/mask in the form a.b.c.d/e.f.g.h where e.f.g.h is a
5315b793 184 netmask in dotted decimal notation. All IP addresses which match the masked
41059f75
AT
185 IP address will be allowed in.
186
187 it() a hostname. The hostname as determined by a reverse lookup will
5315b793 188 be matched (case insensitive) against the pattern. Only an exact
41059f75
AT
189 match is allowed in.
190
191 it() a hostname pattern using wildcards. These are matched using the
192 same rules as normal unix filename matching. If the pattern matches
5315b793 193 then the client is allowed in.
41059f75
AT
194)
195
196You can also combine "hosts allow" with a separate "hosts deny"
197option. If both options are specified then the "hosts allow" option s
5315b793 198checked first and a match results in the client being able to
41059f75
AT
199connect. The "hosts deny" option is then checked and a match means
200that the host is rejected. If the host does not match either the
201"hosts allow" or the "hosts deny" patterns then it is allowed to
202connect.
203
204The default is no "hosts allow" option, which means all hosts can connect.
205
206dit(bf(hosts allow)) The "hosts deny" option allows you to specify a
207list of patterns that are matched against a connecting clients
208hostname and IP address. If the pattern matches then the connection is
209rejected. See the "hosts allow" option for more information.
210
211The default is no "hosts deny" option, which means all hosts can connect.
212
213enddit()
214
215manpagesection(EXAMPLES)
216
217A simple rsyncd.conf file that allow anonymous rsync to a ftp area at
218/home/ftp would be:
219
220verb(
221[ftp]
222 path = /home/ftp
223 comment = ftp export area
224)
225
226
227A more sophisticated example would be:
228
229verb(
230uid = nobody
231gid = nobody
232max connections = 4
233syslog facility = local5
234
235[ftp]
236 path = /var/ftp/pub
237 comment = whole ftp area (approx 6.1 GB)
238
239[sambaftp]
240 path = /var/ftp/pub/samba
241 comment = Samba ftp area (approx 300 MB)
242
243[rsyncftp]
244 path = /var/ftp/pub/rsync
245 comment = rsync ftp area (approx 6 MB)
246
247[sambawww]
248 path = /public_html/samba
249 comment = Samba WWW pages (approx 240 MB)
250
251[cvs]
252 path = /data/cvs
253 comment = CVS repository (requires authentication)
254 auth users = tridge, susan
255 secrets file = /etc/rsyncd.secrets
256)
257
258The /etc/rsyncd.secrets file would look something like this:
259
260verb(
261tridge:mypass
262susan:herpass
263)
264
265manpagefiles()
266
267/etc/rsyncd.conf
268
269manpageseealso()
270
271rsync(1)
272
273manpagediagnostics()
274
275manpagebugs()
276
277The rsync server does not send all types of error messages to the
278client. this means a client may be mystified as to why a transfer
279failed. The error will have been logged by syslog on the server.
280
281Please report bugs! The rsync bug tracking system is online at
282url(http://samba.anu.edu.au/rsync/)(http://samba.anu.edu.au/rsync/)
283
284manpagesection(VERSION)
285This man page is current for version 2.0 of rsync
286
287manpagesection(CREDITS)
288
289rsync is distributed under the GNU public license. See the file
290COPYING for details.
291
292The primary ftp site for rsync is
293url(ftp://samba.anu.edu.au/pub/rsync)(ftp://samba.anu.edu.au/pub/rsync).
294
295A WEB site is available at
296url(http://samba.anu.edu.au/rsync/)(http://samba.anu.edu.au/rsync/)
297
298We would be delighted to hear from you if you like this program.
299
300This program uses the zlib compression library written by Jean-loup
301Gailly and Mark Adler.
302
303manpagesection(THANKS)
304
305Thanks to Warren Stanley for his original idea and patch for the rsync
306server. Thanks to Karsten Thygesen for his many suggestions and
307documentation!
308
309manpageauthor()
310
311rsync was written by Andrew Tridgell and Paul Mackerras. They may be
312contacted via email at tridge@samba.anu.edu.au and
313Paul.Mackerras@cs.anu.edu.au
314