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
* remove most (not all) passive voice
* remove punctuation on bullet points except those under "Case studies" which are a command parameters with a qualifying sentence.
* some minor wording changes for better understanding (for instance "conserved" becomes "preserves")
* added Serge to contributors
Copy file name to clipboardExpand all lines: docs/guides/file_sharing/nfsserver.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,18 +16,18 @@ contributors: Steven Spencer
16
16
17
17
NFS is a client/server protocol: the server provides file system resources for all or part of the network (clients).
18
18
19
-
The communication between clients and server takes place via**R**emote **P**rocedure **C**all (**RPC**) services.
19
+
The communication between clients and server takes place by way of **R**emote **P**rocedure **C**all (**RPC**) services.
20
20
21
21
Remote files are mounted in a directory and appear as a local file system. Client users seamlessly access files shared by the server, browsing directories as if they were local.
22
22
23
23
## Installation
24
24
25
-
2 services are required for NFS to function:
25
+
NFS requires two services to function:
26
26
27
27
* The `network` service (of course);
28
28
* The `rpcbind` service.
29
29
30
-
Service status can be viewed using the commands:
30
+
View the status of the services with the command:
31
31
32
32
```
33
33
systemctl status rpcbind
@@ -39,9 +39,9 @@ If the `nfs-utils` package is not installed:
39
39
sudo dnf install nfs-utils
40
40
```
41
41
42
-
The `nfs-utils` package requires several dependencies, including `rpcbind`, to be installed.
42
+
The `nfs-utils` package requires the installation of several dependencies, including `rpcbind`.
43
43
44
-
The NFS service can be started:
44
+
Start the NFS service with:
45
45
46
46
```
47
47
sudo systemctl enable --now nfs-server rpcbind
@@ -52,7 +52,7 @@ Installing the NFS service creates two users:
@@ -77,14 +77,14 @@ Resource shares are set up in the `/etc/exports` file. Each line in this file co
77
77
***clients**: Clients authorized to access resources;
78
78
***(permissions)**: Permissions on resources.
79
79
80
-
Machines authorized to access resources can be declared by:
80
+
Declare machines authorized to access resources with:
81
81
82
82
***IP address**: `192.168.1.2`
83
83
***Network address**: `192.168.1.0/255.255.255.0` or CIDR format `192.168.1.0/24`
84
84
***FQDN**: client_*.rockylinux.org: allows FQDNs starting with client_ from the rockylinux.org domain;
85
85
*`*` for everybody.
86
86
87
-
Multiple clients can be specified on the same line, separated by a space.
87
+
Specification of multiple clients is possible on the same line separated by a space.
88
88
89
89
### Permissions on resources
90
90
@@ -95,15 +95,15 @@ There are two types of permissions:
95
95
96
96
If no right is specified, then the right applied will be read-only.
97
97
98
-
By default, client user UIDs and GIDs are conserved (except for `root`).
98
+
By default, the NFS server preserves the client user UIDs and GIDs (except for `root`).
99
99
100
100
To force the use of a UID or GID other than that of the user writing the resource, specify the `anonuid=UID` and `anongid=GID` options, or give `anonymous` access to the data with the `all squash` option.
101
101
102
102
!!! warning "warning"
103
103
104
104
There is a parameter, `no_root_squash`, which identifies the client root user as the server root user. This parameter can be dangerous from a system security point of view.
105
105
106
-
By default, the `root_squash` parameter is activated (even if not specified), identifying `root` as an `anonymous` user.
106
+
Activation of the `root_squash` parameter is a default (even if not specified), identifying `root` as an `anonymous` user.
0 commit comments