From 1aae7b222f0600010f8472a617e294e174985211 Mon Sep 17 00:00:00 2001 From: Christian Schwarz Date: Sat, 1 Dec 2018 14:55:22 +0100 Subject: [PATCH] docs: fix confusing description of the role of client identity for sink jobs --- docs/configuration/jobs.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/configuration/jobs.rst b/docs/configuration/jobs.rst index a7bdcae..077784f 100644 --- a/docs/configuration/jobs.rst +++ b/docs/configuration/jobs.rst @@ -57,7 +57,7 @@ using the transport listener type specified in the ``serve`` field of the job co Each transport listener provides a client's identity to the passive side job. It uses the client identity for access control: -* The ``sink`` job only allows pushes to those ZFS filesystems to the active side that are located below ``root_fs/${client_identity}``. +* The ``sink`` job maps requests from different client identities to their respective sub-filesystem tree ``root_fs/${client_identity}``. * The ``source`` job has a whitelist of client identities that are allowed pull access. .. TIP::