Lines Matching full:server

25 Simply put, an NFSv4 server creates a lease for each NFSv4 client.
26 The server collects each client's file open and lock state under
30 While a lease remains valid, the server holding that lease
34 the NFSv4 protocol allows the server to remove the client's open
40 In addition, each NFSv4 server manages a persistent list of client
41 leases. When the server restarts and clients attempt to recover
42 their state, the server uses this list to distinguish amongst
43 clients that held state before the server restarted and clients
45 persist safely across server restarts.
57     server to distinguish successive boot epochs of the same client.
96 the same principal (for example, AUTH_SYS and UID 0), a server is
99 server as if there is one client that is rebooting frequently.
103 distinct principals, the server is likely to allow the first client
108 state recovery after a server or client reboot is not guaranteed.
110 "co_ownerid" string or principal to the server, the server orphans
112 locked files until the server removes the orphaned state.
114 If the server restarts and a client presents a changed "co_ownerid"
115 string or principal to the server, the server will not allow the
134   - NFS-root (diskless) clients, where the local DHCP server (or
143     common NFS server. If hostnames are not assigned centrally
190 Using Kerberos for this purpose enables the client and server to
199 server it accesses. NFSv4 mounts from a Linux NFSv4 client of a
200 particular server then share that lease.