1.\" Copyright (c) 1992, 1993, 1994, 1995
2.\" The Regents of the University of California. All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\" notice, this list of conditions and the following disclaimer in the
11.\" documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\" must display the following acknowledgement:
14.\" This product includes software developed by the University of
15.\" California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\" may be used to endorse or promote products derived from this software
18.\" without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\" @(#)mount_nfs.8 8.3 (Berkeley) 3/29/95
33.\"
| 1.\" Copyright (c) 1992, 1993, 1994, 1995
2.\" The Regents of the University of California. All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\" notice, this list of conditions and the following disclaimer in the
11.\" documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\" must display the following acknowledgement:
14.\" This product includes software developed by the University of
15.\" California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\" may be used to endorse or promote products derived from this software
18.\" without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\" @(#)mount_nfs.8 8.3 (Berkeley) 3/29/95
33.\"
|
34.\" $FreeBSD: head/sbin/mount_nfs/mount_nfs.8 80086 2001-07-21 15:38:37Z iedowse $
| 34.\" $FreeBSD: head/sbin/mount_nfs/mount_nfs.8 81622 2001-08-14 10:01:54Z ru $
|
35.\""
36.Dd March 29, 1995
37.Dt MOUNT_NFS 8
38.Os
39.Sh NAME
40.Nm mount_nfs
41.Nd mount nfs file systems
42.Sh SYNOPSIS
43.Nm
44.Op Fl 23KNPTUbcdilqs
45.Op Fl D Ar deadthresh
46.Op Fl I Ar readdirsize
47.Op Fl L Ar leaseterm
48.Op Fl R Ar retrycnt
49.Op Fl a Ar maxreadahead
50.Op Fl g Ar maxgroups
51.Op Fl m Ar realm
52.Op Fl o Ar options
53.Op Fl r Ar readsize
54.Op Fl t Ar timeout
55.Op Fl w Ar writesize
56.Op Fl x Ar retrans
57.Ar rhost : Ns Ar path node
58.Sh DESCRIPTION
59The
60.Nm
61command
62calls the
63.Xr mount 2
64system call to prepare and graft a remote nfs file system
65.Pq Ar rhost : Ns Ar path
66on to the file system tree at the point
67.Ar node .
68This command is normally executed by
69.Xr mount 8 .
70It implements the mount protocol as described in RFC 1094, Appendix A and
71.%T "NFS: Network File System Version 3 Protocol Specification" ,
72Appendix I.
73.Pp
74By default,
75.Nm
76keeps retrying until the mount succeeds.
77This behaviour is intended for filesystems listed in
78.Xr fstab 5
79that are critical to the boot process.
80For non-critical filesystems, the
81.Fl b
82and
83.Fl R
84flags provide mechanisms to prevent the boot process from hanging
85if the server is unavailable.
86.Pp
87If the server becomes unresponsive while an NFS filesystem is
88mounted, any new or outstanding file operations on that filesystem
89will hang uninterruptibly until the server comes back.
90To modify this default behaviour, see the
91.Fl i
92and
93.Fl s
94flags.
95.Pp
96The options are:
97.Bl -tag -width indent
98.It Fl 2
99Use the NFS Version 2 protocol (the default is to try version 3 first
100then version 2). Note that NFS version 2 has a file size limit of 2
101gigabytes.
102.It Fl 3
103Use the NFS Version 3 protocol.
104.It Fl D
105Used with NQNFS to set the
106.Dq "dead server threshold"
107to the specified number of round trip timeout intervals.
108After a
109.Dq "dead server threshold"
110of retransmit timeouts,
111cached data for the unresponsive server is assumed to still be valid.
112Values may be set in the range of 1 - 9, with 9 referring to an
113.Dq "infinite dead threshold"
114(i.e. never assume cached data still valid).
115This option is not generally recommended and is really an experimental
116feature.
117.It Fl I
118Set the readdir read size to the specified value.
119The value should normally
120be a multiple of DIRBLKSIZ that is <= the read size for the mount.
121.It Fl K
122Pass Kerberos authenticators to the server for client-to-server
123user-credential mapping.
124This requires that the kernel be built with the NFSKERB option.
125The use of this option will prevent the kernel from compiling
126unless calls to the appropriate Kerberos encryption routines
127are provided in the NFS source.
128(Refer to the INTERNET-DRAFT titled
129.%T "Authentication Mechanisms for ONC RPC" ,
130for more information.)
131.It Fl L
132Used with NQNFS to set the lease term to the specified number of seconds.
133Only use this argument for mounts with a large round trip delay.
134Values are normally in the 10-30 second range.
135.It Fl N
136Do
137.Em not
138use a reserved socket port number (see below).
139.It Fl P
140Use a reserved socket port number.
141This flag is obsolete, and only retained for compatibility reasons.
142Reserved port numbers are used by default now.
143This is useful for mounting servers that require clients to use a
144reserved port number on the mistaken belief that this makes NFS
145more secure.
146(For the rare case where the client has a trusted root account
147but untrustworthy users and the network cables are in secure areas this does
148help, but for normal desktop clients this does not apply.)
149.It Fl R
150Set the mount retry count to the specified value.
151The default is a retry count of zero, which means to keep retrying
152forever.
153There is a 60 second delay between each attempt.
154.It Fl T
155Use TCP transport instead of UDP.
156This is recommended for servers that are not on the same LAN cable as
157the client.
| 35.\""
36.Dd March 29, 1995
37.Dt MOUNT_NFS 8
38.Os
39.Sh NAME
40.Nm mount_nfs
41.Nd mount nfs file systems
42.Sh SYNOPSIS
43.Nm
44.Op Fl 23KNPTUbcdilqs
45.Op Fl D Ar deadthresh
46.Op Fl I Ar readdirsize
47.Op Fl L Ar leaseterm
48.Op Fl R Ar retrycnt
49.Op Fl a Ar maxreadahead
50.Op Fl g Ar maxgroups
51.Op Fl m Ar realm
52.Op Fl o Ar options
53.Op Fl r Ar readsize
54.Op Fl t Ar timeout
55.Op Fl w Ar writesize
56.Op Fl x Ar retrans
57.Ar rhost : Ns Ar path node
58.Sh DESCRIPTION
59The
60.Nm
61command
62calls the
63.Xr mount 2
64system call to prepare and graft a remote nfs file system
65.Pq Ar rhost : Ns Ar path
66on to the file system tree at the point
67.Ar node .
68This command is normally executed by
69.Xr mount 8 .
70It implements the mount protocol as described in RFC 1094, Appendix A and
71.%T "NFS: Network File System Version 3 Protocol Specification" ,
72Appendix I.
73.Pp
74By default,
75.Nm
76keeps retrying until the mount succeeds.
77This behaviour is intended for filesystems listed in
78.Xr fstab 5
79that are critical to the boot process.
80For non-critical filesystems, the
81.Fl b
82and
83.Fl R
84flags provide mechanisms to prevent the boot process from hanging
85if the server is unavailable.
86.Pp
87If the server becomes unresponsive while an NFS filesystem is
88mounted, any new or outstanding file operations on that filesystem
89will hang uninterruptibly until the server comes back.
90To modify this default behaviour, see the
91.Fl i
92and
93.Fl s
94flags.
95.Pp
96The options are:
97.Bl -tag -width indent
98.It Fl 2
99Use the NFS Version 2 protocol (the default is to try version 3 first
100then version 2). Note that NFS version 2 has a file size limit of 2
101gigabytes.
102.It Fl 3
103Use the NFS Version 3 protocol.
104.It Fl D
105Used with NQNFS to set the
106.Dq "dead server threshold"
107to the specified number of round trip timeout intervals.
108After a
109.Dq "dead server threshold"
110of retransmit timeouts,
111cached data for the unresponsive server is assumed to still be valid.
112Values may be set in the range of 1 - 9, with 9 referring to an
113.Dq "infinite dead threshold"
114(i.e. never assume cached data still valid).
115This option is not generally recommended and is really an experimental
116feature.
117.It Fl I
118Set the readdir read size to the specified value.
119The value should normally
120be a multiple of DIRBLKSIZ that is <= the read size for the mount.
121.It Fl K
122Pass Kerberos authenticators to the server for client-to-server
123user-credential mapping.
124This requires that the kernel be built with the NFSKERB option.
125The use of this option will prevent the kernel from compiling
126unless calls to the appropriate Kerberos encryption routines
127are provided in the NFS source.
128(Refer to the INTERNET-DRAFT titled
129.%T "Authentication Mechanisms for ONC RPC" ,
130for more information.)
131.It Fl L
132Used with NQNFS to set the lease term to the specified number of seconds.
133Only use this argument for mounts with a large round trip delay.
134Values are normally in the 10-30 second range.
135.It Fl N
136Do
137.Em not
138use a reserved socket port number (see below).
139.It Fl P
140Use a reserved socket port number.
141This flag is obsolete, and only retained for compatibility reasons.
142Reserved port numbers are used by default now.
143This is useful for mounting servers that require clients to use a
144reserved port number on the mistaken belief that this makes NFS
145more secure.
146(For the rare case where the client has a trusted root account
147but untrustworthy users and the network cables are in secure areas this does
148help, but for normal desktop clients this does not apply.)
149.It Fl R
150Set the mount retry count to the specified value.
151The default is a retry count of zero, which means to keep retrying
152forever.
153There is a 60 second delay between each attempt.
154.It Fl T
155Use TCP transport instead of UDP.
156This is recommended for servers that are not on the same LAN cable as
157the client.
|
158(NB: This is NOT supported by most non-BSD servers.)
| 158(NB: This is NOT supported by most
159.No non- Ns Bx
160servers.)
|
159.It Fl U
160Force the mount protocol to use UDP transport, even for TCP NFS mounts.
| 161.It Fl U
162Force the mount protocol to use UDP transport, even for TCP NFS mounts.
|
161(Necessary for some old BSD servers.)
| 163(Necessary for some old
164.Bx
165servers.)
|
162.It Fl a
163Set the read-ahead count to the specified value.
164This may be in the range of 0 - 4, and determines how many blocks
165will be read ahead when a large file is being read sequentially.
166Trying a value greater than 1 for this is suggested for
167mounts with a large bandwidth * delay product.
168.It Fl b
169If an initial attempt to contact the server fails, fork off a child to keep
170trying the mount in the background.
171Useful for
172.Xr fstab 5 ,
173where the filesystem mount is not critical to multiuser operation.
174.It Fl c
175For UDP mount points, do not do a
176.Xr connect 2 .
177This must be used for servers that do not reply to requests from the
178standard NFS port number 2049.
179.It Fl d
180Turn off the dynamic retransmit timeout estimator.
181This may be useful for UDP mounts that exhibit high retry rates,
182since it is possible that the dynamically estimated timeout interval is too
183short.
184.It Fl g
185Set the maximum size of the group list for the credentials to the
186specified value.
187This should be used for mounts on old servers that cannot handle a
188group list size of 16, as specified in RFC 1057.
189Try 8, if users in a lot of groups cannot get response from the mount
190point.
191.It Fl i
192Make the mount interruptible, which implies that file system calls that
193are delayed due to an unresponsive server will fail with EINTR when a
194termination signal is posted for the process.
195.It Fl l
196Used with NQNFS and NFSV3 to specify that the \fBReaddirPlus\fR RPC should
197be used.
198This option reduces RPC traffic for cases such as
199.Dq "ls -l" ,
200but tends to flood the attribute and name caches with prefetched entries.
201Try this option and see whether performance improves or degrades.
202Probably
203most useful for client to server network interconnects with a large bandwidth
204times delay product.
205.It Fl m
206Set the Kerberos realm to the string argument.
207Used with the
208.Fl K
209option for mounts to other realms.
210.It Fl o
211Options are specified with a
212.Fl o
213flag followed by a comma separated string of options.
214See the
215.Xr mount 8
216man page for possible options and their meanings.
217The following NFS specific option is also available:
218.Bl -tag -width indent
219.It port=<port_number>
220Use specified port number for NFS requests.
221The default is to query the portmapper for the NFS port.
222.It acregmin=<seconds>
223.It acregmax=<seconds>
224.It acdirmin=<seconds>
225.It acdirmax=<seconds>
226When attributes of files are cached, a timeout calculated to determine
227whether a given cache entry has expired. These four values determine the
228upper and lower bounds of the timeouts for ``directory'' attributes and
229``regular'' (ie: everything else). The default values are 3 -> 60 seconds
230for regular files, and 30 -> 60 seconds for directories. The algorithm to
231calculate the timeout is based on the age of the file. The older the file,
232the longer the cache is considered valid, subject to the limits above.
233.El
234.Pp
235.Bl -tag -width "dumbtimerXX"
236\fBHistoric \&-o options\fR
237.Pp
238Use of these options is deprecated, they are only mentioned here for
239compatibility with historic versions of
240.Nm .
241.It bg
242Same as
243.Fl b .
244.It conn
245Same as not specifying
246.Fl c .
247.It dumbtimer
248Same as
249.Fl d .
250.It intr
251Same as
252.Fl i .
253.It kerb
254Same as
255.Fl K .
256.It nfsv2
257Same as
258.Fl 2 .
259.It nfsv3
260Same as
261.Fl 3 .
262.It rdirplus
263Same as
264.Fl l .
265.It mntudp
266Same as
267.Fl U .
268.It resvport
269Same as
270.Fl P .
271.It seqpacket
272Same as
273.Fl p .
274.It nqnfs
275Same as
276.Fl q .
277.It soft
278Same as
279.Fl s .
280.It tcp
281Same as
282.Fl T .
283.El
284.It Fl q
285Use the Not Quite NFS (NQNFS) protocol.
286This experimental protocol is NFS Version 2 with leasing extensions
287similar to those found in NFS Version 3.
288The interoperability of this protocol with other systems is
289very limited and its implementation is not widely used.
290Do not use this option unless you know exactly what you are doing!
291.It Fl r
292Set the read data size to the specified value.
293It should normally be a power of 2 greater than or equal to 1024.
294This should be used for UDP mounts when the
295.Dq "fragments dropped due to timeout"
296value is getting large while actively using a mount point.
297(Use
298.Xr netstat 1
299with the
300.Fl s
301option to see what the
302.Dq "fragments dropped due to timeout"
303value is.)
304See the
305.Fl w
306option as well.
307.It Fl s
308A soft mount, which implies that file system calls will fail
309after \fBRetry\fR round trip timeout intervals.
310.It Fl t
311Set the initial retransmit timeout to the specified value.
312May be useful for fine tuning UDP mounts over internetworks
313with high packet loss rates or an overloaded server.
314Try increasing the interval if
315.Xr nfsstat 1
316shows high retransmit rates while the file system is active or reducing the
317value if there is a low retransmit rate but long response delay observed.
318(Normally, the -d option should be specified when using this option to manually
319tune the timeout
320interval.)
321.It Fl w
322Set the write data size to the specified value.
323Ditto the comments w.r.t. the
324.Fl r
325option, but using the
326.Dq "fragments dropped due to timeout"
327value on the server instead of the client.
328Note that both the
329.Fl r
330and
331.Fl w
332options should only be used as a last ditch effort at improving performance
333when mounting servers that do not support TCP mounts.
334.It Fl x
335Set the retransmit timeout count for soft mounts to the specified value.
336.El
337.Sh SEE ALSO
338.Xr mount 2 ,
339.Xr unmount 2 ,
340.Xr fstab 5 ,
341.Xr mount 8 ,
342.Xr nfsd 8 ,
343.Xr nfsiod 8 ,
344.Xr showmount 8
345.Sh BUGS
346Due to the way that Sun RPC is implemented on top of UDP (unreliable datagram)
347transport, tuning such mounts is really a black art that can only be expected
348to have limited success.
349For clients mounting servers that are not on the same
350LAN cable or that tend to be overloaded,
351TCP transport is strongly recommended,
| 166.It Fl a
167Set the read-ahead count to the specified value.
168This may be in the range of 0 - 4, and determines how many blocks
169will be read ahead when a large file is being read sequentially.
170Trying a value greater than 1 for this is suggested for
171mounts with a large bandwidth * delay product.
172.It Fl b
173If an initial attempt to contact the server fails, fork off a child to keep
174trying the mount in the background.
175Useful for
176.Xr fstab 5 ,
177where the filesystem mount is not critical to multiuser operation.
178.It Fl c
179For UDP mount points, do not do a
180.Xr connect 2 .
181This must be used for servers that do not reply to requests from the
182standard NFS port number 2049.
183.It Fl d
184Turn off the dynamic retransmit timeout estimator.
185This may be useful for UDP mounts that exhibit high retry rates,
186since it is possible that the dynamically estimated timeout interval is too
187short.
188.It Fl g
189Set the maximum size of the group list for the credentials to the
190specified value.
191This should be used for mounts on old servers that cannot handle a
192group list size of 16, as specified in RFC 1057.
193Try 8, if users in a lot of groups cannot get response from the mount
194point.
195.It Fl i
196Make the mount interruptible, which implies that file system calls that
197are delayed due to an unresponsive server will fail with EINTR when a
198termination signal is posted for the process.
199.It Fl l
200Used with NQNFS and NFSV3 to specify that the \fBReaddirPlus\fR RPC should
201be used.
202This option reduces RPC traffic for cases such as
203.Dq "ls -l" ,
204but tends to flood the attribute and name caches with prefetched entries.
205Try this option and see whether performance improves or degrades.
206Probably
207most useful for client to server network interconnects with a large bandwidth
208times delay product.
209.It Fl m
210Set the Kerberos realm to the string argument.
211Used with the
212.Fl K
213option for mounts to other realms.
214.It Fl o
215Options are specified with a
216.Fl o
217flag followed by a comma separated string of options.
218See the
219.Xr mount 8
220man page for possible options and their meanings.
221The following NFS specific option is also available:
222.Bl -tag -width indent
223.It port=<port_number>
224Use specified port number for NFS requests.
225The default is to query the portmapper for the NFS port.
226.It acregmin=<seconds>
227.It acregmax=<seconds>
228.It acdirmin=<seconds>
229.It acdirmax=<seconds>
230When attributes of files are cached, a timeout calculated to determine
231whether a given cache entry has expired. These four values determine the
232upper and lower bounds of the timeouts for ``directory'' attributes and
233``regular'' (ie: everything else). The default values are 3 -> 60 seconds
234for regular files, and 30 -> 60 seconds for directories. The algorithm to
235calculate the timeout is based on the age of the file. The older the file,
236the longer the cache is considered valid, subject to the limits above.
237.El
238.Pp
239.Bl -tag -width "dumbtimerXX"
240\fBHistoric \&-o options\fR
241.Pp
242Use of these options is deprecated, they are only mentioned here for
243compatibility with historic versions of
244.Nm .
245.It bg
246Same as
247.Fl b .
248.It conn
249Same as not specifying
250.Fl c .
251.It dumbtimer
252Same as
253.Fl d .
254.It intr
255Same as
256.Fl i .
257.It kerb
258Same as
259.Fl K .
260.It nfsv2
261Same as
262.Fl 2 .
263.It nfsv3
264Same as
265.Fl 3 .
266.It rdirplus
267Same as
268.Fl l .
269.It mntudp
270Same as
271.Fl U .
272.It resvport
273Same as
274.Fl P .
275.It seqpacket
276Same as
277.Fl p .
278.It nqnfs
279Same as
280.Fl q .
281.It soft
282Same as
283.Fl s .
284.It tcp
285Same as
286.Fl T .
287.El
288.It Fl q
289Use the Not Quite NFS (NQNFS) protocol.
290This experimental protocol is NFS Version 2 with leasing extensions
291similar to those found in NFS Version 3.
292The interoperability of this protocol with other systems is
293very limited and its implementation is not widely used.
294Do not use this option unless you know exactly what you are doing!
295.It Fl r
296Set the read data size to the specified value.
297It should normally be a power of 2 greater than or equal to 1024.
298This should be used for UDP mounts when the
299.Dq "fragments dropped due to timeout"
300value is getting large while actively using a mount point.
301(Use
302.Xr netstat 1
303with the
304.Fl s
305option to see what the
306.Dq "fragments dropped due to timeout"
307value is.)
308See the
309.Fl w
310option as well.
311.It Fl s
312A soft mount, which implies that file system calls will fail
313after \fBRetry\fR round trip timeout intervals.
314.It Fl t
315Set the initial retransmit timeout to the specified value.
316May be useful for fine tuning UDP mounts over internetworks
317with high packet loss rates or an overloaded server.
318Try increasing the interval if
319.Xr nfsstat 1
320shows high retransmit rates while the file system is active or reducing the
321value if there is a low retransmit rate but long response delay observed.
322(Normally, the -d option should be specified when using this option to manually
323tune the timeout
324interval.)
325.It Fl w
326Set the write data size to the specified value.
327Ditto the comments w.r.t. the
328.Fl r
329option, but using the
330.Dq "fragments dropped due to timeout"
331value on the server instead of the client.
332Note that both the
333.Fl r
334and
335.Fl w
336options should only be used as a last ditch effort at improving performance
337when mounting servers that do not support TCP mounts.
338.It Fl x
339Set the retransmit timeout count for soft mounts to the specified value.
340.El
341.Sh SEE ALSO
342.Xr mount 2 ,
343.Xr unmount 2 ,
344.Xr fstab 5 ,
345.Xr mount 8 ,
346.Xr nfsd 8 ,
347.Xr nfsiod 8 ,
348.Xr showmount 8
349.Sh BUGS
350Due to the way that Sun RPC is implemented on top of UDP (unreliable datagram)
351transport, tuning such mounts is really a black art that can only be expected
352to have limited success.
353For clients mounting servers that are not on the same
354LAN cable or that tend to be overloaded,
355TCP transport is strongly recommended,
|
352but unfortunately this is restricted to mostly 4.4BSD servers.
| 356but unfortunately this is restricted to mostly
357.Bx 4.4
358servers.
|
| |