Can we add an example to the manpage?

Something to match the already existing example for NFS ("Example 18  
Setting sharenfs Property Options on a ZFS File System").

eric

On Sep 26, 2007, at 4:05 PM, Tim Haley - Sun Microsystem wrote:

> I am sponsoring this fast-track for Mark Shellenbaum.
> Requested binding is micro, timeout 10/03/2007.
>
> Template Version: @(#)sac_nextcase 1.64 07/13/07 SMI
> This information is Copyright 2007 Sun Microsystems
> 1. Introduction
>     1.1. Project/Component Working Name:
>        ZFS sharesmb property
>     1.2. Name of Document Author/Supplier:
>        Author:  Mark Shellenbaum
>     1.3  Date of This Document:
>       26 September, 2007
> 4. Technical Description
>
> OVERVIEW:
>
>         ZFS needs a way to handle "smb" shares.  ZFS already has  
> the sharenfs
>         property, we need to create a "sharesmb" to handle smb shares.
>
> PROPOSED SOLUTION:
>
>         Create a property "sharesmb" that will allow for datasets  
> to be
>         shared via "smb".
>
> Manpage changes:
>
> 348c348,349
> <      must be lowercase, except for "mountpoint" and "sharenfs".
> ---
>>      must be lowercase, except for "mountpoint", "sharenfs" and
>>      "sharesmb".
> 650a652
>>      sharesmb=on | off | opts
> 651a654,683
>>          Controls whether the file system is shared via SMB,  and
>>          what  options  are  used.  A file system with a sharesmb
>>          property of "off" is managed through  traditional  tools
>>          such  as  sharemgr(1M).  Otherwise,  the  file  system  is
>>          automatically  shared  and unshared  with  the  "zfs  share"
>>          and "zfs unshare" commands. If the property is set  to   
>> "on",
>>          the  sharemgr(1M) command  is  invoked  with  no  options.
>>          Otherwise, the sharemgr(1M) command is invoked with options
>>          equivalent  to the contents of this property.
>>
>>          Due to the requirement that SMB shares must have a  
>> resource name,
>>          a unique resource name will be constructed from the data  
>> set name.
>>          The constructed name will be a copy of the dataset name  
>> except that
>>          characters in the dataset name which would be illegal in the
>>         resource name are replaced with underscore (_) characters.  A  
>> pseudo
>>          property "name" is also supported that allows the  
>> administrator to
>>          replace the data set name with a specified name. The  
>> specified name
>>         is then used to replace the prefix dataset in the case of
>>          inheritance. For example, if the dataset "data/home/john"  
>> is set
>>          with name=john, then data/home/john will have a resource  
>> name of
>>          john .  If there is a sub dataset of data/home/john/ 
>> backups, it
>>          will then have a  resource name of john_backups.
>>
>>          When the "sharesmb" property is changed for  a  dataset,
>>          the dataset and any children inheriting the property are
>>          re-shared with the new options, only if the property was
>>          previously "off", or if they were shared before the pro-
>>          perty was changed. If the new  property  is  "off",  the
>>          file systems are unshared.
>>
>>
> 1491,1492c1523,1524
> <          "sharenfs"  property.  File  systems are shared when the
> <          "sharenfs" property is set.
> ---
>>          "sharenfs" and "sharesmb"  properties.  File  systems are
>>          shared when the "sharenfs" or "sharesmb" property is set.
> 1739a1772
>>        pool/home/bob  sharesmb       off                    default
>
>
> 6. Resources and Schedule
>     6.4. Steering Committee requested information
>       6.4.1. Consolidation C-team Name:
>               ON
>     6.5. ARC review type: FastTrack
>     6.6. ARC Exposure: open
>


Reply via email to