Commit c094d932 authored by Wayne Davison's avatar Wayne Davison

Documented the new "outgoing chmod" daemon option.

parent aaccaa88
......@@ -263,12 +263,22 @@ only superficially equivalent to the client specifying the
bf(--include-from) option with a equivalent file.
See the "exclude" option above.
dit(bf(incoming chmod)) This option allows you to specify a chmod string
that will affect the permissions of all incoming files (files that are
being copied to the daemon). These changes happen last, giving you the
final word on what the permissions should look like in the repository. See
the description of the bf(--chmod) rsync option and the bf(chmod) manpage
for information on the format of this string.
dit(bf(incoming chmod)) This option allows you to specify a set of
comma-separated chmod strings that will affect the permissions of all
incoming files (files that are being received by the daemon). These
changes happen last, giving this setting the final word on what the
permissions should look like in the repository.
See the description of the bf(--chmod) rsync option and the bf(chmod)
utility's manpage for information on the format of this string.
dit(bf(outgoing chmod)) This option allows you to specify a set of
comma-separated chmod strings that will affect the permissions of all
outgoing files (files that are being sent out from the daemon). These
changes happen first, making the sent permissions appear to be different
than those stored in the filesystem itself (which, for instance, you
could disable group write permissions on the server).
See the description of the bf(--chmod) rsync option and the bf(chmod)
utility's manpage for information on the format of this string.
dit(bf(auth users)) The "auth users" option specifies a comma and
space-separated list of usernames that will be allowed to connect to
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment