Lines Matching +full:protocol +full:- +full:node

1 .. SPDX-License-Identifier: GPL-2.0
7 This document explains how the NFSv4 protocol identifies client
19 ------------
21 The NFSv4 protocol uses "lease-based file locking". Leases help
34 the NFSv4 protocol allows the server to remove the client's open
48 ------------------------
54   - co_ownerid: An arbitrary but fixed string.
56   - boot verifier: A 64-bit incarnation verifier that enables a
72   - The "co_ownerid" string identifies the client during reboot
75   - The "co_ownerid" string helps servers distinguish the client
79   - Because it often appears on the network in the clear, the
82   - The content of the "co_ownerid" string is set and unchanging
84   - The NFSv4 protocol places a 1024-byte limit on the size of the
88 ----------------------------
124 ------------------------------------------
128 the client's UTS node name (the same node name, incidentally, that
131 the node name by itself is not adequately unique, and can change
134   - NFS-root (diskless) clients, where the local DHCP server (or
137   - "Containers" within a single Linux host.  If each container has
142   - Clients across multiple administrative domains that access a
161 Note that this file is empty on name-space creation. If the
162 container system has access to some sort of per-container identity
166     sha256sum /etc/machine-id | awk '{print $1}' \\
170 -----------------------
186 control this behavior. Alternately, a single-user client with a
193 flavor with Kerberos and the integrity QOS to prevent in-transit
197 ----------------
202 Once a client establishes open and lock state, the NFSv4 protocol
213   - nfs(5)
214   - kerberos(7)
215   - RFC 7530 for the NFSv4.0 specification
216   - RFC 8881 for the NFSv4.1 specification.