Configuration of nfs_server |
modules/NfsServer.ycp |
NFS server configuration data, I/O functions. | |
|
|
This module has an unstable interface. |
Imports
Global VariablesGlobal Functions
Local Variables |
Function sets internal variable, which indicates, that any settings were modified, to "true"
Functions which returns if the settings were modified
- Return value:
-
settings were modified
Required packages for this module to operate
Write only, used during autoinstallation. Don't run services and SuSEconfig, it's all done at one place.
Enable nfsv4
GSS Security ?
Domain name to be used for nfsv4 (idmapd.conf)
Should the server be started? New since 9.0: Exports are independent of this setting.
- Example
-
[ $[ "mountpoint": "/projects", "allowed": [ "*.local.domain(ro)", "@trusted(rw)"] ], $[ ... ], ... ]
Do we have nfslock? (nfs-utils: yes, nfs-server: no)
Get all NFS server configuration from a map. When called by nfs_server_auto (preparing autoinstallation data) the map may be empty.
- Parameters:
-
settings $["start_nfsserver": "nfs_exports":]
- Return value:
-
success
- See
-
exports
Set the variables just as is and without complaining
- Parameters:
-
settings $[ start_nfsserver:, nfs_exports:, ]
Dump the NFS settings to a map, for autoinstallation use.
- Return value:
-
$["start_nfsserver": "nfs_exports":]
- See
-
exports
Reads NFS settings from the SCR (.etc.exports)
- Return value:
-
true on success
Saves /etc/exports and creates missing directories.
- Return value:
-
true on success
Saves NFS server configuration. (exports(5)) Creates any missing directories.
- Return value:
-
true on success
- Return value:
-
A summary for autoyast
Return required packages for auto-installation
- Return value:
-
of packages to be installed and to be removed