Lines Matching +full:loss +full:- +full:of +full:- +full:lock

9 Since then two more major releases of NFS have been published, with NFSv3
14 and work is in progress on adding support for minor version 1 of the NFSv4
17 The purpose of this document is to provide information on some of the
18 special features of the NFS client that can be configured by system
26 string.  File open and lock state shared between one client and one server
34 over the lifetime of a client system.  Node names can have other
36 work well as part of an nfs_client_id4 string.
39 used instead of a system's node name when an NFS client identifies itself to
42 or loss of state during NFS reboot recovery or transparent state migration.
50 The string should remain fixed for the lifetime of the client.  It can be
52 outstanding NFSv4 state has expired, to prevent loss of NFSv4 state.
64 migrated onto another server by means of the special "fs_locations"
68 …530 Section 6\: Filesystem Migration and Replication: https://tools.ietf.org/html/rfc3530#section-6
69 …lementation Guide for Referrals in NFSv4: https://tools.ietf.org/html/draft-ietf-nfsv4-referrals-00
71 The fs_locations information can take the form of either an ip address and
77 /var/lib/nfs/rpc_pipefs, the upcall consists of the following steps:
85        - the cache name, "dns_resolve"
86        - the hostname to resolve
89        writes the result into the rpc_pipefs pseudo-file
97        <hostname> is identical to the second argument of the helper
98        script, and <ttl> is the 'time to live' of this cache entry (in
99        units of seconds).
111 .. code-block:: sh
127     [ $# -lt 2 ] && die
134             result="$(${getent} hosts ${name} | ${cut} -f1 -d\ )"
135             [ -z "${result}" ] && result="0"