@@ -12,7 +12,7 @@ Send Options
|
12 | 12 | :ref:`Source<job-source>` and :ref:`push<job-push>` jobs have an optional ``send`` configuration section. |
13 | 13 | |
14 | 14 | :: |
15 | | - |
| 15 | + |
16 | 16 | jobs: |
17 | 17 | - type: push |
18 | 18 | filesystems: ... |
@@ -84,8 +84,8 @@ If ``encrypted=false``, zrepl expects that filesystems matching ``filesystems``
|
84 | 84 | |
85 | 85 | .. _job-send-options-properties: |
86 | 86 | |
87 | | -``properties`` |
88 | | --------------- |
| 87 | +``send_properties`` |
| 88 | +------------------- |
89 | 89 | Sends the dataset properties along with snapshots. |
90 | 90 | Please be careful with this option and read the :ref:`note on property replication below <job-note-property-replication>`. |
91 | 91 | |
@@ -171,7 +171,7 @@ You can send the original properties from the first receiver to another receiver
|
171 | 171 | A Note on Property Replication |
172 | 172 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
173 | 173 | |
174 | | -If a send stream contains properties, as per ``send.properties`` or ``send.backup_properties``, |
| 174 | +If a send stream contains properties, as per ``send.send_properties`` or ``send.backup_properties``, |
175 | 175 | the default ZFS behavior is to use those properties on the receiving side, verbatim. |
176 | 176 | |
177 | 177 | In many use cases for zrepl, this can have devastating consequences. |
@@ -221,6 +221,14 @@ and property replication is enabled, the receiver must :ref:`inherit the followi
|
221 | 221 | * ``keyformat`` |
222 | 222 | * ``encryption`` |
223 | 223 | |
| 224 | +Sharing |
| 225 | +------- |
| 226 | + |
| 227 | +You may not want the replicated filesystem shared in the same way as the source is. |
| 228 | + |
| 229 | +* ``sharenfs`` |
| 230 | +* ``sharesmb`` |
| 231 | + |
224 | 232 | .. _job-recv-options--placeholder: |
225 | 233 | |
226 | 234 | Placeholders |
|