- buster 2.7.1-2
- buster-backports 3.4-1~bpo10+1
- testing 3.4-1
- unstable 3.4-1
GANESHA-CONFIG(8) | NFS-Ganesha | GANESHA-CONFIG(8) |
NAME¶
ganesha-config - NFS Ganesha Configuration FileSYNOPSIS¶
/etc/ganesha/ganesha.conf
DESCRIPTION¶
NFS-Ganesha obtains configuration data from the configuration file:The configuration file consists of following parts:
Comments¶
Empty lines and lines starting with '#' are comments.:# This whole line is a comment Protocol = TCP; # The rest of this line is a comment
Blocks¶
Related options are grouped together into "blocks". A block is a name followed by parameters enclosed between "{" and "}". A block can contain other sub blocks as well.:EXPORT { Export_ID = 1; FSAL { Name = VFS: } }
NOTE: FSAL is a sub block. Refer to BLOCKS section for list of blocks and options.
Options¶
Configuration options can be of following types.1. Numeric. Numeric options can be defined in octal, decimal, or hexadecimal. The format follows ANSI C syntax. eg.:
mode = 0755; # This is octal 0755, 493 (decimal)
Numeric values can also be negated or logical NOT'd. eg.:
anonymousuid = -2; # this is a negative mask = ~0xff; # Equivalent to 0xffffff00 (for 32 bit integers)
2. Boolean. Possible values are true, false, yes and no. 1 and 0 are not acceptable.
3. List. The option can contain a list of possible applicable values. Protocols = 3, 4, 9p;
Including other config files¶
Additional files can be referenced in a configuration using '%include' and '%url' directives.:%include <filename> %url <url, e.g., rados://mypool/mynamespace/myobject>
The included file is inserted into the configuration text in place of the %include or %url line. Sub-inclusions may be to any depth. Filenames and URLs may optionally use '"':
%include base.conf %include "base.conf" %url rados://mypool/mynamespace/myobject %url "rados://mypool/mynamespace/myobject" %url rados://mypool/myobject %url "rados://mypool/myobject"
In the case of rados:// URLs, providing a two-component URL indicates that the default namespace should be used.
BLOCKS¶
NFS-Ganesha supports the following blocks:EXPORT {}¶
Along with its configuration options, the EXPORT block supports FSAL and CLIENT sub-blocks. See ganesha-export-config(8) for usage of this block and its sub-blocks.EXPORT_DEFAULTS {}¶
Refer to ganesha-export-config(8) for usageMDCACHE {}¶
Refer to ganesha-cache-config(8) for usageNFS_CORE_PARAM {}¶
Refer to ganesha-core-config(8) for usageNFS_IP_NAME {}¶
Refer to ganesha-core-config(8) for usageNFS_KRB5 {}¶
Refer to ganesha-core-config(8) for usageNFSv4 {}¶
Refer to ganesha-core-config(8) for usageCEPH {}¶
Refer to ganesha-ceph-config(8) for usage9P {}¶
Refer to ganesha-9p-config(8) for usageGLUSTER {}¶
Refer to ganesha-gluster-config(8) for usageGPFS {}¶
Refer to ganesha-gpfs-config(8) for usageLOG {}¶
Refer to ganesha-log-config(8) for usage1.**LOG { FACILITY {} }** 2.**LOG { FORMAT {} }**
PROXY {}¶
Refer to ganesha-proxy-config(8) for usageRGW {}¶
Refer to ganesha-rgw-config(8) for usageVFS {}¶
Refer to ganesha-vfs-config(8) for usageXFS {}¶
Refer to ganesha-xfs-config(8) for usageEXAMPLE¶
Along with "ganesha.conf", for each installed FSAL, a sample config file is added at:/etc/ganesha
SEE ALSO¶
ganesha-log-config(8) ganesha-rgw-config(8) ganesha-vfs-config(8) ganesha-lustre-config(8) ganesha-xfs-config(8) ganesha-gpfs-config(8) ganesha-gluster-config(8) ganesha-9p-config(8) ganesha-proxy-config(8) ganesha-ceph-config(8) ganesha-core-config(8) ganesha-export-config(8)March 24, 2021 |