Lines Matching +full:client +full:- +full:id
43 the client side.
46 for each client to server mount point that is maintained until an umount.
47 If the connection breaks, the client will attempt a reconnect with a new
49 The client side can operate without any daemons running, but performance
50 will be improved by running nfsiod daemons that perform read-aheads
51 and write-behinds.
68 The client side mount_nfs along with portmap and
75 from client, etc.) to various interoperability problems between different
80 require the \fB-n\fR option to enable non-root mount request servicing.
96 On the client side, there are several mount options useful for dealing
99 \fB-b\fR
105 \fBmount -a\fR
108 option should not be used so that the client will wait for the server to
111 with various non-BSD NFS servers. The
112 \fB-P\fR
114 client use a reserved IP port number to satisfy some servers' security
118 such the BSD server does not require a client to use a reserved port number.
121 \fB-c\fR
122 option stops the NFS client from doing a \fIconnect\fR on the UDP
130 \fB-g=\fInum\fR
140 \fB-g=\fInum\fR
152 There are several mount options available to help a client deal with
159 when processes on the client that access files in the file system do not
160 tolerate file I/O systems calls that return -1 with \fIerrno == EINTR\fR
165 A soft mount (\fB-s\fR option) retries an RPC \fIn\fR
167 system call returns -1 with errno set to EINTR.
176 \fB-x=\fInum\fR
182 An interruptible mount (\fB-i\fR option) checks to see if a termination signal
207 sending the RPC reply message back to the client, it can be highly variable
214 on the server when non-idempotent RPCs are redone [Juszczak89].
232 options on the client side that can prove useful when trying to
235 \fB-r=\fInum\fR
237 \fB-w=\fInum\fR
245 reported by the \fIip:\fR section of a \fBnetstat -s\fR
246 command on either the client or server.
248 fun figuring out which client(s) are involved.
254 By default, the 4.4BSD NFS client dynamically estimates the retransmit
257 \fB-d\fR
259 the dynamic estimation of retransmit timeout, so that the client will
266 \fB-t=\fInum\fR
268 \fB-d\fR
302 unless the client or server processor runs at less than 5-10MIPS. For a
304 significant and TCP transport may only be useful when the client
315 certain network interconnects is \fB-a=\fInum\fR
317 attempt to read-ahead during sequential reading of a file. The default value
324 Under some workloads, a buffer cache of 4-6Mbytes can result in significant
325 performance improvements over 1-2Mbytes, both in client side system call
342 For ordinary NFS, the server receives client credentials
343 in the RPC request as a user id
352 local file system mount point and client host address basis and cannot refer to
360 read-only.
361 For each host or group of hosts, the file system can be exported read-only or
363 You can also define one of three client user id to server credential
365 Root (user id == 0) can be mapped to some default credentials while all other
367 If the default credentials for user id equal zero
370 user id == 0 to the credentials for the user nobody.
371 Since the client user id and group id list is used unchanged on the server
373 the user id and group id space must be common between the client and server.
374 (ie. user id N on the client must refer to the same user on the server)
387 \fIleases\fR [Gray89] with delayed write client caching,
390 the \fB-q\fR mount option is specified.
392 transport (\fB-T\fR).
405 such as counts of the various different RPCs and cache hit rates on the client
415 On the client side, the fields in the \fIRpc Info:\fR section are of particular
417 The \fITimedOut\fR field is the number of I/O system calls that returned -1
438 IP fragments being dropped (gateway, client or server)
443 The \fBnetstat -s\fR comes in useful during investigation of RPC transport
453 There is a RPC activity logging facility for both the client and
456 one, the logs in the kernel structures nfsrtt (for the client side)
462 \fIlog\fR[pos - 1] are in chronological order.
469 .sh 1 "Diskless Client Support"
471 The NFS client does include kernel support for diskless/dataless operation
473 A diskless/dataless client is configured using a version of the
491 diskless_offset.c - This little program reads a ``kernel'' object file and
494 be compiled/linked in funny ways depending on the client architecture.
497 diskless_setup.c - This program is run on the server and sets up files for a
498 given client. It mostly just fills in an nfs_diskless structure and
500 /var/diskless/setup.<official-hostname>
502 diskless_boot.c - There are two functions in here that may be used
508 separate "setup.<official-hostname>" file so that there is only
511 /var/diskless/boot.<official-hostname> to control the netboot.
515 make a "kernel" for the client(s) with mountroot() == nfs_mountroot()
523 nfs_diskless structure for that client.
525 kernel file (the -x option) or
526 saved in /var/diskless/setup.<official-hostname>.
532 file called /var/diskless/boot.<official-hostname>
544 Create a /var subtree for each client in an appropriate place on the server,
545 such as /var/diskless/var/<client-hostname>/...
546 By using the <client-hostname> to differentiate /var for each host,