Edward Abrams edited this page Apr 6, 2018 · 6 revisions

Table of Contents


nfs-ganesha has a few dependencies. On a red-hat based linux distribution, this should be enough for most of it:

 # Common things
 yum install gcc git cmake autoconf libtool bison flex
 # More nfs-ganesha specific
 yum install libgssglue-devel openssl-devel nfs-utils-lib-devel doxygen redhat-lsb gcc-c++

If you run into cmake problems get the source and compile it on your system:

 $ sudo yum install cmake flex bison
 $ wget
 $ tar zxf cmake-
 $ cd cmake-
 $ ./configure --prefix=/usr/ && gmake && sudo gmake install

Compiling NFS-GANESHA with cmake (v2+)

With cmake things are pretty straightforward:

 mkdir build
 ccmake ../path/to/nfs-ganesha/src
 # set options there, such as selecting which FSAL you want to enable.
 # Alternatively, this can be done with cmake ../path/to/nfs-ganesha/src -DUSE_FSAL_XYZ=ON or OFF
 make install

Configuration files examples are provided in nfs-ganesha/src/config_samples

Compiling NFS-GANESHA with autotools (v1.x.y)

Since version 1.0.1, there are different ways of compiling NFS-GANESHA

Producing a statically linked daemon

You have to specify a FSAL name when compiling. If none is provided, then FSAL/PROXY will be used. The name you can use are POSIX, SNMP, PROXY and FUSE Example: compiling NFS-GANESHA with FSAL/POSIX

  # ./configure --with-fsal=POSIX
  # make
  # make install

This way of compiling is the one used for all 0.99.xy releases. In the NFS-GANESHA packages, the binary whose names is similar to xfs.ganehsa.nfsd or posix.ganeshell are compiled this way.

Producing a dynamically linked daemon

Procedure is very similar as the one stated above, you just have to add option --enable-buildsharedfsal when using ./configure Example: compiling NFS-GANESHA with FSAL/XFS and dynamic FSAL

  # ./configure --with-fsal=XFS --enable-buildsharedfsal
  # make
  # make install

This will produce a dynamic FSAL library and a NFS-GANESHA daemon linked with this dynamic FSAL. This feature is available since release 1.0.1 . FSAL compiled as shared library are pretty useful when used with FSAL-less NFS_GANESHA daemon

Producing a FSAL-less daemon

This is available only with version 1.0.1 and later. This feature was not implemented all 0.99.xy versions. This method produces the NFS-GANESHA binary with no FSAL. The daemon looks in the configuration file for the location of a FSAL library and loads it at runtime using the dlopen() API. This way, you can produce a very generic NFS_GANESHA daemon that can be used to access various filesystems. You just need to have the related FSAL to be loaded. The compilation is done this way

  # ./configure --with-fsal=DYNFSAL
  # make
  # make install

You will produce binaries dynfsal.ganesha.nfsd and dynfsal.ganeshell. See document about the configuration of such binaries (in the documentation section of this website) for instructions on how to use this kind of daemon.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.