[SCM] The rsync repository. - branch master updated
Rsync CVS commit messages <[email protected]> Mon, 16 May 2011 20:32:57 +0200 (CEST)
| Newsgroups | gmane.network.rsync.cvs |
|---|---|
| Message-ID | <[email protected]> |
The branch, master has been updated
via b9cc2d4 Explicitly mention spaces in the "path" setting.
from ac30d22 Check for linux/falloc.h header file.
;a=shortlog;h=master
- Log -----------------------------------------------------------------
commit b9cc2d4c868df195878f22dd1c5e9f9d21451971
Author: Wayne Davison <[email protected]>
Date: Mon May 16 11:24:07 2011 -0700
Explicitly mention spaces in the "path" setting.
-----------------------------------------------------------------------
Summary of changes:
rsyncd.conf.yo | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
Changeset truncated at 500 lines:
diff --git a/rsyncd.conf.yo b/rsyncd.conf.yo
index 49d2522..35d269f 100644
--- a/rsyncd.conf.yo
+++ b/rsyncd.conf.yo
@@ -156,6 +156,12 @@ For example, this would use the authorizing user's name in the path:
verb( path = /home/%RSYNC_USER_NAME% )
+It is fine if the path includes internal spaces -- they will be retained
+verbatim (which means that you shouldn't try to escape them). If your final
+directory has a trailing space (and this is somehow not something you wish to
+fix), append a trailing slash to the path to avoid losing the trailing
+whitespace.
+
dit(bf(use chroot)) If "use chroot" is true, the rsync daemon will chroot
to the "path" before starting the file transfer with the client. This has
the advantage of extra protection against possible implementation security
--
The rsync repository.