From: Steve Dickson <SteveD@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Cc: Linux NFSv4 mailing list <nfsv4@linux-nfs.org>
Subject: [Patch 7/9] New nfsmount.conf(5) man page
Date: Mon, 09 Mar 2009 17:06:42 -0400 [thread overview]
Message-ID: <49B584E2.9000608@RedHat.com> (raw)
In-Reply-To: <49B57FB2.9020000@RedHat.com>
commit 5232a0cbb7d7b1eb64dfb3f282b42d1ff5fd586a
Author: Steve Dickson <steved@redhat.com>
Date: Mon Mar 9 14:08:57 2009 -0400
The new nfsmount.conf(5) man page and the update to
the nfs(5) man page
Signed-off-by: Steve Dickson <steved@redhat.com>
diff --git a/utils/mount/Makefile.am b/utils/mount/Makefile.am
index de810a4..a586edc 100644
--- a/utils/mount/Makefile.am
+++ b/utils/mount/Makefile.am
@@ -5,7 +5,7 @@
sbindir = /sbin
man8_MANS = mount.nfs.man umount.nfs.man
-man5_MANS = nfs.man
+man5_MANS = nfs.man nfsmount.conf.man
sbin_PROGRAMS = mount.nfs
EXTRA_DIST = nfsmount.x $(man8_MANS) $(man5_MANS) nfsmount.conf
diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
index 13de524..1700c5b 100644
--- a/utils/mount/nfs.man
+++ b/utils/mount/nfs.man
@@ -752,6 +752,36 @@ In the presence of multiple client network interfaces,
special routing policies,
or atypical network topologies,
the exact address to use for callbacks may be nontrivial to determine.
+.SH "MOUNT CONFIGURATION FILE"
+All of the mount options described the above section can also be set
+in the
+.B /etc/nfsmount.conf
+file. The configuration file is made up of three different
+sections: Global, Server and MountPoint. See
+.B nfsmount.conf(5)
+for details.
+.PP
+The mount command parses section in a particular order and
+will not use options that have been set in previous sections.
+The order of precedence is as follows:
+is:
+.HP
+.B Command line option
+- options set on the command will always be used.
+.HP
+.B Mount Point options
+- options set in the '<Mount_Point>' section will be
+used only if they are not specified on the command line.
+.HP
+.B Sever options
+- options set in the '<Server_Name>' section will be used if
+they are not specified on the command line section or
+the mount point section.
+.HP
+.B Global options
+- options set in the '[NFSMount_Global_Options]' will be used
+if they are not specified on the command or in the mount
+point section or the server section.
.SH EXAMPLES
To mount an export using NFS version 2,
use the
diff --git a/utils/mount/nfsmount.conf.man b/utils/mount/nfsmount.conf.man
new file mode 100644
index 0000000..fddd018
--- /dev/null
+++ b/utils/mount/nfsmount.conf.man
@@ -0,0 +1,68 @@
+.\"@(#)nfsmount.conf.5"
+.TH NFSMOUNT.CONF 5 "9 Mar 2008"
+.SH NAME
+nfsmount.conf - Configuration file for NFS mounts
+.SH SYNOPSIS
+Configuration file for NFS mounts that allow mount options
+to be set globally, per server or per mount point.
+.SH DESCRIPTION
+The configuration file is made up of multiple sections
+followed by variables associated with that section.
+A section is define by a string enclosed by '[' and ']'
+branches, similar to '[nfs.server.com]'.
+Variables are assignment statements that assign values
+to particular variables using a '=' sign,
+similar to 'Proto=Tcp'.
+Sections are broken up into three basic categories:
+Global options, Server options and Mount Point options.
+.HP
+.BR [NFSMount_Global_Options]
+- This statically named section
+defines all of the global mount options that can be
+applied on every NFS mount.
+.HP
+.BR [<Server_Name>]
+- This section defines all the mount options that should
+be used on mounts to a particular NFS server. The '<Sever_Name>'
+needs to be an exact match of server name in the
+mount command.
+.HP
+.BR [<Mount_Point>]
+- This section defines all the mount options that
+should be used on a particular mount point.
+The '<Mount_Point>' string need to be an exact match of the
+path in the mount command.
+.SH EXAMPLES
+.PP
+These are some example lines of how sections and variables
+are define in the configuration file.
+.PP
+[NFSMount_Global_Options]
+.br
+Proto=Tcp
+.PP
+The TCP protocol will be used on every NFS mount.
+.PP
+[nfsserver.foo.com]
+.br
+rsize=32k
+.br
+wsize=32k
+.PP
+A 33k (32768 bytes) block size will be used as the read and write
+size on all mounts to the 'nfsserver.foo.com' server.
+.PP
+[/export/home]
+.br
+Background=True
+.PP
+All mounts to the '/export/home' export will put in
+background (i.e. done asynchronously).
+.SH FILES
+.TP 10n
+.I /etc/nfsmount.conf
+Default NFS mount configuration file
+.PD
+.SH SEE ALSO
+.BR nfs (5),
+.BR mount (8),
next prev parent reply other threads:[~2009-03-09 21:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 20:44 [Patch 0/9] NFS Mount Configuration File Steve Dickson
2009-03-09 20:47 ` [Patch 1/9] Make idmapd's Configuration Parsing Code Available Steve Dickson
2009-03-09 20:50 ` [Patch 2/9] Ignore blanks in section definitions and before assignment statements Steve Dickson
2009-03-09 20:52 ` [Patch 3/9] Ensure configuration values are stored in lower case Steve Dickson
2009-03-09 20:58 ` [Patch 4/9] Mount support routines used to convert mount options Steve Dickson
2009-03-09 21:03 ` [Patch 5/9] Hooks needs incorporate file configuration code Steve Dickson
2009-03-09 21:04 ` [Patch 6/9] An example of an nfsmount.conf file Steve Dickson
2009-03-09 21:06 ` Steve Dickson [this message]
2009-03-09 21:08 ` [Patch 8/9] Another way to define the configuration file Steve Dickson
2009-03-09 21:10 ` [Patch 9/9] Fixed a couple nits Steve Dickson
2009-03-09 21:49 ` [Patch 0/9] NFS Mount Configuration File Chuck Lever
2009-03-17 19:44 ` Steve Dickson
2009-03-17 20:17 ` Chuck Lever
2009-03-17 20:25 ` J. Bruce Fields
2009-03-17 20:36 ` Chuck Lever
2009-03-18 13:07 ` Steve Dickson
2009-03-18 16:31 ` Chuck Lever
2009-03-18 18:10 ` Steve Dickson
[not found] ` <49C13928.8040806-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-03-19 11:13 ` Steve Dickson
[not found] ` <49C228D3.4070005-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-03-19 15:45 ` J. Bruce Fields
2009-03-19 16:37 ` Chuck Lever
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49B584E2.9000608@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox