Browse Source

technical_behavior_and_limitations.md

Antonio SJ Musumeci 1 day ago
parent
commit
483fcde3c9
  1. 3
      mkdocs/docs/faq/technical_behavior_and_limitations.md

3
mkdocs/docs/faq/technical_behavior_and_limitations.md

@ -231,7 +231,8 @@ side `default_permissions` option and leaving it to the FUSE
server. When default permissions is enabled the kernel will do the server. When default permissions is enabled the kernel will do the
entitlement checks and only allow requests through which have been entitlement checks and only allow requests through which have been
allowed. When not enabled it is the responsibility of the FUSE server, allowed. When not enabled it is the responsibility of the FUSE server,
in this case mergerfs, to do that.
in this case mergerfs, to do whatever is necessary to manage
entitlements.
Prior to mergerfs v2.42.0 it would enable `default_permissions` but Prior to mergerfs v2.42.0 it would enable `default_permissions` but
also leveraged the uid and gid available in each FUSE request. The also leveraged the uid and gid available in each FUSE request. The

Loading…
Cancel
Save