+holes, but it has the disadvantages of requiring super-user privileges,
+of not being able to follow symbolic links outside of the new root path
+when reading, and of complicating the preservation of usernames and groups
+(see below). When "use chroot" is false, for security reasons,
+symlinks may only be relative paths pointing to other files within the root
+path, and leading slashes are removed from absolute paths. The default for
+"use chroot" is true.
+
+In order to preserve usernames and groupnames, rsync needs to be able to
+lookup the IDs using getpuid() and getpgid(). This means that the chroot
+area will need to have copies of your user/group information (edited, if
+desired) inside the chroot tree for rsync to use (the traditional files
+are /etc/passwd and /etc/group). If the needed files are not available,
+rsync will only be able to copy the IDs, just as if the --numeric-ids
+option had been specified.
+
+dit(bf(max connections)) The "max connections" option allows you to
+specify the maximum number of simultaneous connections you will allow.
+Any clients connecting when the maximum has been reached will receive a
+message telling them to try later. The default is 0 which means no limit.
+See also the "lock file" option.
+
+dit(bf(lock file)) The "lock file" option specifies the file to use to
+support the "max connections" option. The rsync server uses record
+locking on this file to ensure that the max connections limit is not
+exceeded for the modules sharing the lock file.
+The default is tt(/var/run/rsyncd.lock).