| mount_nfs.8 (80086) | mount_nfs.8 (81622) |
|---|---|
| 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. --- 17 unchanged lines hidden (view full) --- 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. --- 17 unchanged lines hidden (view full) --- 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 --- 107 unchanged lines hidden (view full) --- 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 --- 107 unchanged lines hidden (view full) --- 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 --- 174 unchanged lines hidden (view full) --- 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 --- 174 unchanged lines hidden (view full) --- 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. |