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.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are nfs_package and nfs_service supposed to specify the NFS-client or -server package/service?
For RHEL, the default service of this module is "nfs", which is the NFS-server service for RHEL. (For client behavior, I haven't found one.)
For SLES 11, the default service of this module is "nfs", which is the NFS-client service for SLES. In addition there's "nfsserver".
Also for RHEL package "nfs-utils" description says: "NFS utilities and supporting clients and daemons for the kernel NFS server"
For SLES, there's different packages for: "nfs-client" and "nfs-kernel-server".
Maybe a split between NFS-client and NFS-server functionality would be reasonable?
I started investigation, because I did not want to make NFS-servers out of all machines, which should work as NFS-clients. (See also issue #33 .) It'd be good, to handle this within a single module in my opinion.
This issue is to clarify the direction, not necessarily already about implementation.
The text was updated successfully, but these errors were encountered:
Are nfs_package and nfs_service supposed to specify the NFS-client or -server package/service?
For RHEL, the default service of this module is "nfs", which is the NFS-server service for RHEL. (For client behavior, I haven't found one.)
For SLES 11, the default service of this module is "nfs", which is the NFS-client service for SLES. In addition there's "nfsserver".
Also for RHEL package "nfs-utils" description says: "NFS utilities and supporting clients and daemons for the kernel NFS server"
For SLES, there's different packages for: "nfs-client" and "nfs-kernel-server".
Maybe a split between NFS-client and NFS-server functionality would be reasonable?
I started investigation, because I did not want to make NFS-servers out of all machines, which should work as NFS-clients. (See also issue #33 .) It'd be good, to handle this within a single module in my opinion.
This issue is to clarify the direction, not necessarily already about implementation.
The text was updated successfully, but these errors were encountered: