@@ -1333,10 +1333,12 @@ expand it.
13331333
133413340 . ` --confine-root=DIR `
13351335
1336- This bounds where the paths listed under [ ` --insecure-links ` ] ( #opt ) are
1337- allowed to resolve: one that ends up outside DIR is refused, even if every
1338- symlink along it was owned by a trusted user. The ownership walk asks who
1339- planted a link; this asks where the path came out.
1336+ In the default symlink mode this bounds where operator option paths and
1337+ paths selected from a [ ` --files-from ` ] ( #opt ) list are allowed to resolve:
1338+ one that ends up outside DIR is refused, even if every symlink along it was
1339+ owned by a trusted user. Explicit source roots remain operator-selected
1340+ transfer roots. The ownership walk asks who planted a link; this asks where
1341+ the path came out.
13401342
13411343 DIR must be absolute. Nothing is confined by default, and
13421344 ` --confine-root=/ ` is a no-op.
@@ -2251,8 +2253,12 @@ expand it.
22512253 See the [ ` --max-size ` ] ( #opt ) option for a description of how SIZE can be
22522254 specified. The default suffix if none is given is bytes.
22532255
2254- Beginning in 3.2.7, a value of 0 is an easy way to specify SIZE_MAX (the
2255- largest limit possible).
2256+ A value of 0 means the largest limit this build supports. It resolves to
2257+ the same ceiling an explicit SIZE is checked against, so it cannot select
2258+ a limit higher than one that could be written explicitly. The literal 0 is
2259+ passed to the remote rsync, allowing each peer to resolve it for its own
2260+ word size. A daemon administrator can refuse all client-supplied values,
2261+ including 0, with ` refuse options = max-alloc ` .
22562262
22572263 You can set a default value using the environment variable
22582264 [ ` RSYNC_MAX_ALLOC ` ] ( # ) using the same SIZE values as supported by this
0 commit comments