Create a new group with specified name. If -n is specified, the command checks only the validity of the command and that the group does not already exist. If no protocol is specified, all known protocols are enabled for the specified group. If a protocol is specified, only that protocol is enabled. You can specify properties for a specified protocol. If group exists, use of -P adds the specified protocol to that group. As an example of the create subcommand, the following command creates a new group with the name mygroup.

# sharemgr create mygroup

Delete the specified group. If the group is not empty, you can use the -f option to force the deletion, which unshares and removes all shares from the group before removing the group itself. If you specify a protocol, rather than deleting the whole group, this subcommand deletes the protocol from the group. The -n option can be used to test the syntax of the command. As an example, the following command removes the group mygroup from the configuration if it is empty.

# sharemgr delete mygroup

# sharemgr delete -f mygroup

List the defined groups. If a protocol is specified, list only those groups that have the specified protocol defined. If the verbose option is specified, the current state of the group and all protocols enabled on the group are listed as well. For example:

# sharemgr list -v
mygroup enabled nfs
rdonlygrp disabled nfs

Shows the contents of the specified group(s). If the verbose option is specified, the resource name and description of each share is displayed if they are defined. Otherwise, only the share paths are displayed. Also, when temporary shares are listed, they are prefixed with an asterisk (*). If the -p option is specified, all options defined for the protocols of the group are displayed, in addition to the display without options. If the -P option is used, the output is limited to those groups that have the specified protocol enabled. If the -x option is specified, output is in XML format and the -p and -v options are ignored, because all information is included in the XML. The following example illustrates the use of the -p option.

# sharemgr show -p mygroup
default nfs=()
 * /data/backup
mygroup nfs=(nosuid=true)
 /export/home/home0
 /export/home/home1

# sharemgr show -v mygroup
mygroup
 HOME0=/export/home/home0 "Home directory set 0"
 HOME1=/export/home/home1 "Home directory set 1"

# sharemgr show -vp zfs
zfs nfs=()
 zfs/ztest
 /ztest
 /ztest/backups

Set protocol-specific properties on the specified group. The -P option is required and must specify a valid protocol. Optionsets are protocol-specific sets of properties that can be negotiated by the protocol client. For NFS, optionsets are equivalent to security modes as defined in nfssec(5). If -S optionset is specified, the properties are applied to the selected optionset. Otherwise they are applied to the general optionset. Together, -P and -S select a specific view of the group's options on which to work. Property values are strings. A specified property is set to a new value if the property already exists or is added to the protocol if it does not already exist. In the general case, at least one property must be set. If -S is specified, properties can be omitted and the specified optionset is enabled for the protocol. The -s option allows setting properties on a per-share basis. While this is supported, it should be limited to managing legacy shares and to the occasional need for an override of a group-level property or placing an additional property on one share within a group. An example of this subcommand:

# sharemgr set -P nfs -p anon=1234 mygroup

Unset the specified properties for the protocol or for the specified optionset of the protocol. In the general case, at least one property must be set. If -S is specified, properties can be omitted and the specified optionset is removed from the protocol. The -s option allows removing a share-specific property. An example of this subcommand:

# sharemgr unset -P nfs -p anon mygroup

Add a new share to the specified group. The -s option is mandatory and takes a full directory path. If either or both of -d and -r are specified, they specify values associated with the share. -d provides a description string to document the share and -r provides a protocol-independent resource name. Resource names are not used by NFS at this time but can be specified. These names currently follow the same naming rules as group names. The temporary option (-t) results in the share being shared but not stored in the configuration repository. This option is intended for shares that should not survive a reboot or server restart, or for testing purposes. Temporary shares are indicated in the show subcommand output with an asterisk (*) preceding the share. If sharepath is a ZFS path and that path is added to the zfs group, sharemgr creates a new ZFS subgroup; the new share is added to that subgroup. Any ZFS sub-filesystems under the ZFS filesystem designated by sharepath will inherit the shared status of sharepath. The effect of the add-share subcommand on a ZFS dataset is determined by the values of the sharesmb and sharenfs properties of that dataset. See zfs(1M) for a description of the sharesmb and sharenfs properties. The following are examples of the add-share subcommand.

# sharemgr add-share -s /export/home/home0 -d "home \e
directory set 0" -r HOME0 mygroup

# sharemgr add-share -s /export/home/home1 -d "home \e
directory set 1" -r HOME1 mygroup

Move the specified share from the group it is currently in to the specified destination group. The move-share subcommand does not create a group. A specified group must exist for the command to succeed. The following is an example of this subcommand.

# sharemgr move-share -s /export/home/home1 newgroup

Remove the specified share from the specified group. The force (-f) option forces the share to be removed even if it is busy. You must specify the full path for sharepath. For group, use the subgroup as displayed in the output of the sharemgr show command. Note that if there are subshares that were created by inheritance, these will be removed, along with the parent shares.

Set or change the specified share's description and resource values. One use of set-share is to rename a resource. The syntax for this use of the subcommand is:

# sharemgr set-share -r current_name=new_name -s sharepath group

Enable the specified group(s), or (with -a) all groups, and start sharing the contained shares. This state persists across reboots. An enabled group will be shared whenever the corresponding SMF service instance is enabled. sharemgr will start the SMF service instance if it is not currently online.

Disable the specified group(s), or (with -a) all groups, and unshare the shares that they contain. This state persists across reboots. A disabled group will not be shared even if the corresponding SMF service instance is online. This feature is useful when you do not want a group of shares to be started at boot time.

Start the specified group, or (with -a) all groups. The start subcommand is similar to enable in that all shares are started, but start works only on groups that are enabled. start is used by the SMF to start sharing at system boot. A group will not start sharing if it is in the sharemgr disabled state. However, the corresponding SMF service instance will be started. Note that the start subcommand is similar to the shareall(1M) command in that it starts up only the configured shares. That is, the enabled shares will start being shared, but the configuration state is left the same. The command:

# sharemgr start -a

# shareall

Stop the specified group, or (with -a) all groups. The stop subcommand is similar to disable in that all shares are no longer shared, but it works only on groups that are enabled. stop is used by the SMF to stop sharing at system shutdown. Note that the stop subcommand is similar to the unshareall(1M) command in that all active shares are unshared, but the configuration is left the same. That is, the shares are stopped but the service instances are left enabled. The command:

# sharemgr stop -a

# unshareall

Shares the specified path in the default share group. This subcommand implements the share(1M) functionality. Shares that are shared in this manner will be transient shares. Use of the -p option causes the shares to be persistent.

Unshares the specified share. This subcommand implements the unshare(1M) functionality. By default, the unshare is temporary. The -p option is provided to remove the share from the configuration in a way that persists across reboots.

Values of type boolean take either true or false.

Values of type value take a numeric value.

Values of type file take a file name and not a file path.

Values of type access-list are described in detail following the descriptions of the NFS properties.

Set the access-based enumeration (ABE) policy for a share. When set to true, ABE filtering is enabled on this share and directory entries to which the requesting user has no access will be omitted from directory listings returned to the client. When set to false or not defined, ABE filtering will not be performed on this share. This property is not defined by default. disabled

Allows the NFS server to do access control for NFS Version 2 clients (running SunOS 2.4 or earlier). When aclok is set on the server, maximum access is given to all clients. For example, with aclok set, if anyone has read permissions, then everyone does. If aclok is not set, minimum access is given to all clients.

Specifies the AD container in which to publish shares. The AD container is specified as a comma-separated list of attribute name-value pairs using the LDAP distinguished name (DN) or relative distinguished name (RDN) format. The DN or RDN must be specified in LDAP format using the cn=, ou=, and dc= prefixes:

Set uid to be the effective user ID of unknown users. By default, unknown users are given the effective user ID UID_NOBODY. If uid is set to -1, access is denied.

CATIA V4 uses characters in file names that are considered to be invalid by Windows. CATIA V5 is available on Windows. A CATIA V4 file could be inaccessible to Windows clients if the file name contains any of the characters that are considered illegal in Windows. By default, CATIA character substitution is not performed. If the catia property is set to true, the following character substitution is applied to file names.

CATIA CATIA
V4 UNIX V5 Windows
 " \e250 0x00a8 Dieresis
 * \e244 0x00a4 Currency Sign
 / \e370 0x00f8 Latin Small Letter O with Stroke
 : \e367 0x00f7 Division Sign
 < \e253 0x00ab Left-Pointing Double Angle Quotation Mark
 > \e273 0x00bb Right-Pointing Double Angle Quotation Mark
 ? \e277 0x00bf Inverted Question Mark
 \e \e377 0x00ff Latin Small Letter Y with Dieresis
 | \e246 0x00a6 Broken Bar

Set the share to attempt to use end-to-end checksums. The value cksumlist specifies the checksum algorithms that should be used.

Set the client-side caching policy for a share. Client-side caching is a client feature and offline files are managed entirely by the clients.

The following are valid values for the csc property:

Set the guest access policy for the share. When set to true guest access is allowed on this share. When set to false or not defined guest access is not allowed on this share. This property is not defined by default. An idmap(1M) name-based rule can be used to map guest to any local username, such as guest or nobody. If the local account has a password in /var/smb/smbpasswd the guest connection will be authenticated against that password. Any connection made using an account that maps to the local guest account will be treated as a guest connection. Example name-based rule:

# idmap add winname:Guest unixuser:guest

Load file rather than a listing of the directory containing this file when the directory is referenced by an NFS URL.

Enables NFS server logging for the specified system. The optional tag determines the location of the related log files. The tag is defined in etc/nfs/nfslog.conf. If no tag is specified, the default values associated with the global tag in etc/nfs/nfslog.conf is used. Support of NFS server logging is available only for NFS Version 2 and Version 3 requests.

Prevents clients from mounting subdirectories of shared directories. For example, if /export is shared with the nosub option on server wool then an NFS client cannot do:

# mount -F nfs wool:/export/home/mnt

By default, clients are allowed to create files on a shared file system with the setuid or setgid mode enabled. Specifying nosuid causes the server file system to silently ignore any attempt to enable the setuid or setgid mode bits.

Moves the location of the public file handle from root (/) to the exported directory for WebNFS-enabled browsers and clients. This option does not enable WebNFS service; WebNFS is always on. Only one file system per server can have the public property. You can apply the public property only to a share and not to a group.

Where charset is one of: euc-cn, euc-jp, euc-jpms, euc-kr, euc-tw, iso8859-1, iso8859-2, iso8859-5, iso8859-6, iso8859-7, iso8859-8, iso8859-9, iso8859-13, iso8859-15, koi8-r. Clients that match the access-list for one of these properties will be assumed to be using that character set and file and path names will be converted to UTF-8 for the server.

Sharing is read-only to the clients listed in access-list; overrides the rw suboption for the clients specified. See the description of access-list below.

Sharing is read-write to the clients listed in access-list; overrides the ro suboption for the clients specified. See the description of access-list below.

Access is not allowed to any client that matches the access list. The exception is when the access list is an asterisk (*), in which case ro or rw can override none.

Only root users from the hosts specified in access-list have root access. See details on access-list below. By default, no host has root access, so root users are mapped to an anonymous user ID (see the anon=uid option described above). Netgroups can be used if the file system shared is using UNIX authentication (AUTH_SYS).

For a client that is allowed root access, map the root UID to the specified user id.

When sharing with sec=dh (see nfssec(5)), set the maximum lifetime (in seconds) of the RPC request's credential (in the authentication header) that the NFS server allows. If a credential arrives with a lifetime larger than what is allowed, the NFS server rejects the request. The default value is 30000 seconds (8.3 hours). This property is ignored for security modes other than dh.

Sharing is read-only to the clients listed in access-list; overrides the rw suboption for the clients specified. See the description of access-list below.

Sharing is read-write to the clients listed in access-list; overrides the ro suboption for the clients specified. See the description of access-list below.

Access is not allowed to any client that matches the access list. The exception is when the access list is an asterisk (*), in which case ro or rw can override none.

The name of a host. With a server configured for DNS or LDAP naming in the nsswitch.conf(4) hosts entry, a hostname must be represented as a fully qualified DNS or LDAP name.

A netgroup contains a number of hostnames. With a server configured for DNS or LDAP naming in the nsswitch.conf(4) hosts entry, any hostname in a netgroup must be represented as a fully qualified DNS or LDAP name.

To use domain membership the server must use DNS or LDAP, rather than, for example, NIS or NIS+, to resolve hostnames to IP addresses. That is, the hosts entry in the nsswitch.conf(4) must specify dns or ldap ahead of nis or nisplus, because only DNS and LDAP return the full domain name of the host. Other name services, such as NIS or NIS+, cannot be used to resolve hostnames on the server because, when mapping an IP address to a hostname, they do not return domain information. For example, for the IP address 172.16.45.9: NIS or NIS+

rw=.mydomain.mycompany.com

rw=.

The network or subnet component is preceded by an at-sign (@). It can be either a name or a dotted address. If a name, it is converted to a dotted address by getnetbyname(3SOCKET). For example:

=@mynet

=@172.16 or =@172.16.0.0

=@theothernet/17 or =@172.16.132/22

Successful completion.

Service is offline and cannot be enabled (start only).

Command failed.

Error codes used for exit status.