Skip to content

NFS Mount Configuration File

Steve Dickson linux-nfs 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest9 patches 11 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/9Make idmapd's Configuration Parsing Code Availablesupport/include/Makefile.am support/include/conffile.h support/nfs/Makefile.am +5 more+27 -270 replies
2/9Ignore blanks in section definitions and before assignment statementssupport/nfs/conffile.c+26 -90 replies
3/9Ensure configuration values are stored in lower casesupport/nfs/conffile.c+20 -50 replies
4/9Mount support routines used to convert mount optionsutils/mount/Makefile.am utils/mount/configfile.c+300 -10 replies
5/9Hooks needs incorporate file configuration code.utils/mount/mount.c+12 -10 replies
6/9An example of an nfsmount.conf fileutils/mount/Makefile.am utils/mount/nfsmount.conf+121 -10 replies
7/9New nfsmount.conf(5) man pageutils/mount/Makefile.am utils/mount/nfs.man utils/mount/nfsmount.conf.man+99 -10 replies
8/9Another way to define the configuration fileconfigure.ac+10 -00 replies
9/9Fixed a couple nitssupport/nfs/conffile.c utils/idmapd/idmapd.c utils/mount/configfile.c+3 -30 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [Patch 0/9] NFS Mount Configuration File

Hello,

The following patch set introduces a configuration file where mount options can be define. The options in the file can be applied globally or per server or per mount point.

The patch set reuses the configuration parsing code that idmapd uses. I did added a couple enhancements like ignoring blanks in certain definitions as well as at the beginning of assignment statements.

There are man pages include in the patch set but in a nut shell, the configuration file has three basic types of sections. A global section, server section and mount point section. There can only be one global section and multiple server and mount point sections.

The mount command prioritize these sections in the following way:
* Options on the command line are always used.

* Options defined in the mount point section are used as long a the options are not in the command line options.

* Options defined in the server section are used as long as they are not defined on the command line or in the mount point section.

* Options defined in the global section are used as long as the options are not on the command line or in the mount point section or in the server section.

This is the first step toward moving the default NFS version from 3 to 4 on the client. Having a configuration file which allows users to define the maximum and minimum NFS versions that should be negotiated is the right thing to do... IMHO.. Even though this patch does not does not do that, it does lay the ground work for that type of functionality.

Comments?

steved.