/etc/exports: Difference between revisions
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
==/etc/exports.d== | ==/etc/exports.d== | ||
After reading <tt>/etc/exports</tt>, exportfs reads files in the <tt>/etc/exports.d</tt> directory as extra export tables. Only files ending in .exports are considered. Files beginning with a dot are ignored. The format for extra export tables is the same as <tt>/etc/exports<tt>. | After reading <tt>/etc/exports</tt>, exportfs reads files in the <tt>/etc/exports.d</tt> directory as extra export tables. Only files ending in .exports are considered. Files beginning with a dot are ignored. The format for extra export tables is the same as <tt>/etc/exports</tt>. | ||
=Example= | =Example= | ||
Latest revision as of 13:19, 16 May 2017
Internal
Overview
/etc/exports contains a table of local physical file systems on an NFS server that are accessible to NFS clients. The contents of the file are maintained by the server's system administrator. Each file system in this table has a list of options and an access control list. The table is used by exportfs command.
/etc/exports.d
After reading /etc/exports, exportfs reads files in the /etc/exports.d directory as extra export tables. Only files ending in .exports are considered. Files beginning with a dot are ignored. The format for extra export tables is the same as /etc/exports.
Example
/volume1/wiki 192.168.1.2(rw,async,no_wdelay,no_root_squash,insecure_locks,sec=sys,anonuid=0,anongid=0) /volume3/dropbox 192.168.1.0/24(rw,async,no_wdelay,no_root_squash,insecure_locks,sec=sys,anonuid=0,anongid=0)