X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/ef3f14e6a74a36a428f6d38aa77fc7fff2b6c576..ec8637f3679b891041c798400774141024e24a4e:/rsyncd.conf.yo

diff --git a/rsyncd.conf.yo b/rsyncd.conf.yo
index b3eb4dd8..b914570d 100644
--- a/rsyncd.conf.yo
+++ b/rsyncd.conf.yo
@@ -1,5 +1,5 @@
 mailto(rsync-bugs@samba.org)
-manpage(rsyncd.conf)(5)(8 Nov 2007)()()
+manpage(rsyncd.conf)(5)(16 Dec 2007)()()
 manpagename(rsyncd.conf)(configuration file for rsync in daemon mode)
 manpagesynopsis()
 
@@ -113,6 +113,10 @@ After the global options you should define a number of modules, each
 module exports a directory tree as a symbolic name. Modules are
 exported by specifying a module name in square brackets [module]
 followed by the options for that module.
+The module name cannot contain a slash or a closing square bracket.  If the
+name contains whitespace, each internal sequence of whitespace will be
+changed into a single space, while leading or trailing whitespace will be
+discarded.
 
 startdit()
 
@@ -180,7 +184,7 @@ as long as that directory does not exist.  When this option is enabled,
 rsync will refuse to run if that path is a directory or a symlink to
 a directory.  When using the "munge symlinks" option in a chroot area,
 you should add this path to the exclude setting for the module so that
-the user can't try to create it.
+a user can't try to create it.
 
 Note:  rsync makes no attempt to verify that any pre-existing symlinks in
 the hierarchy are as safe as you want them to be.  If you setup an rsync
@@ -651,7 +655,7 @@ url(http://rsync.samba.org/)(http://rsync.samba.org/)
 
 manpagesection(VERSION)
 
-This man page is current for version 3.0.0pre5 of rsync.
+This man page is current for version 3.0.0pre7 of rsync.
 
 manpagesection(CREDITS)