Table of Contents
Advertisement
"Filesystem Properties" on page 382
■
TFTP 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 TFTP protocol (sharetftp), 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
■
Access Control Lists for Filesystems
You can set options to control ACL behavior as well as control access to the root directory of
the filesystem.
Note -
For more information about ACLs, see the following topics:
"Root Directory Access" on page 415
■
"ACL Behavior on Mode Change" on page 416
■
"ACL Inheritance Behavior" on page 417
■
"Root Directory ACL" on page 419
■
Root Directory Access
To set basic access control for the root directory of the filesystem, go to Shares > Shares >
filesystem > Access. These settings can be managed in-band via whatever protocols are being
used, but they can also be specified here for convenience. These properties cannot be changed
on a read-only filesystem, as they require changing metadata for the root directory of the
filesystem.
User - The owner of the root directory. This can be specified as a user ID or user name. For
■
more information on mapping UNIX and Windows users, see
based NFS access, this can be changed from the client using the chown command.
ACLs are available only for filesystems.
Access Control Lists for Filesystems
Identity
Mapping. For UNIX-
Shares and Projects
415
Advertisement
Table of Contents
