Share and Project Protocols
For example, if a client attempts to open a file for read/write access but the ACL grants only
read access, that open request will fail but that file will still be included in the list of entries.
For more information about ACLs, see “Access Control Lists for Filesystems” on page 415.
HTTP Protocol
Each share has protocol-specific properties that define the behavior of different protocols for
that share. These properties can be defined for each share or inherited from a share's project.
For the HTTP protocol (sharedav), users can set the share mode to determine if the filesystem
is available for read only (ro), read and write (rw or on), or neither (off).
Related Topics
■
“Project Properties” on page 376
■
“Filesystem Properties” on page 382
FTP Protocol
Each share has protocol-specific properties that define the behavior of different protocols for
that share. These properties can be defined for each share or inherited from a share's project.
For the FTP protocol (shareftp), users can set the share mode to determine if the filesystem is
available for read only (ro), read and write (rw or on), or neither (off).
Related Topics
■
“Project Properties” on page 376
■
“Filesystem Properties” on page 382
SFTP Protocol
Each share has protocol-specific properties that define the behavior of different protocols for
that share. These properties can be defined for each share or inherited from a share's project.
For the SFTP protocol (sharesftp), users can set the share mode to determine if the filesystem
is available for read only (ro), read and write (rw or on), or neither (off).
Related Topics
■
“Project Properties” on page 376
414 Oracle ZFS Storage Appliance Administration Guide, Release OS8.6.x • September 2016
To Next Page
Loading...
Need help?
General
