Automatic File System Sharing

In the Oracle Solaris 11 release, the share command creates permanent shares that are automatically shared during system startup. Unlike previous releases, you will not need to edit the /etc/dfs/dfstab file to record the information about shares for subsequent reboots. The /etc/dfs/dfstab is no longer used.

Table 5-1 File-System Sharing Task Map

How to Set Up Automatic File-System Sharing

1. Become an administrator.

   For more information, see How to Obtain Administrative Rights in Oracle Solaris Administration: Security Services.

2. Define the file systems to be shared.

   Use the share command to define each path to be shared. This information will be retained when a system is rebooted.

   # share -F nfs -o specific-options pathname

   See the share_nfs(1M) man page for a complete list of the specific-options.

3. Verify that the information is correct.

   Run the share command to check that the correct options are listed:

   # share -F nfs
   -        /export/share/man   sec=sys,ro   ""
   -        /usr/src     sec=sys,rw=eng   ""
   -        /export/ftp    sec=sys,ro,public  ""

See Also

The next step is to set up your autofs maps so that clients can access the file systems that you have shared on the server. For more information, see Task Overview for Autofs Administration.

How to Enable WebNFS Access

Note the following:

• By default all file systems that are available for NFS mounting are automatically available for WebNFS access. The only condition that requires the use of this procedure is one of the following:

  • To allow NFS mounting on a server that does not currently allow NFS mounting

  • To reset the public file handle to shorten NFS URLs by using the public option with the share command

  • To force a specific HTML file to be loaded by using the index option with the share command

• You can also use the sharectl utility to configure file-sharing protocols, such as NFS. See the sharectl(1M) man page and sharectl Command.

See Planning for WebNFS Access for a list of issues to consider before starting the WebNFS service.

1. Become an administrator.

   For more information, see How to Obtain Administrative Rights in Oracle Solaris Administration: Security Services.

2. Define the file systems to be shared by the WebNFS service.

   Use the share command to define each file system. The public and index tags that are shown in the following example are optional.

   # share -F nfs -o ro,public,index=index.html /export/ftp

   See the share_nfs(1M) man page for a complete list of options.

3. Verify that the information is correct.

   Run the share command to check that the correct options are listed:

   # share -F nfs
   -        /export/share/man   sec=sys,ro   ""
   -        /usr/src     sec=sys,rw=eng   ""
   -        /export/ftp    sec=sys,ro,public,index=index.html  ""

How to Enable NFS Server Logging

1. Become an administrator.

   For more information, see How to Obtain Administrative Rights in Oracle Solaris Administration: Security Services.

2. (Optional) Change file system configuration settings.

   In /etc/nfs/nfslog.conf, you can change the settings in one of two ways. You can edit the default settings for all file systems by changing the data that is associated with the global tag. Alternately, you can add a new tag for this file system. If these changes are not needed, you do not need to change this file. The format of /etc/nfs/nfslog.conf is described in the nfslog.conf(4) man page.

3. Define the file systems to use NFS server logging.

   Use the share command to define each file system. The tag that is used with the log=tag option must be entered in /etc/nfs/nfslog.conf. This example uses the default settings in the global tag.

   # share -F nfs -ro,log=global /export/ftp

4. Verify that the information is correct.

   Run the share command to check that the correct options are listed:

   # share -F nfs
   -        /export/share/man   sec=sys,ro   ""
   -        /usr/src     sec=sys,rw=eng   ""
   -        /export/ftp    sec=sys,ro,public,log=global  ""

5. Check if nfslogd, the NFS log daemon, is running.

   # ps -ef | grep nfslogd

6. (Optional) Start nfslogd, if it is not running.

   # svcadm restart network/nfs/server:default