diff options
| author | neilbrown <neilbrown> | 2000-02-04 03:34:35 +0000 |
|---|---|---|
| committer | neilbrown <neilbrown> | 2000-02-04 03:34:35 +0000 |
| commit | c0e89b264fb01c5b4bb925b32d1b6b7764c44d4a (patch) | |
| tree | 0477c8518fb801df159fe21f8b535c0be072c492 /utils/exportfs | |
| parent | d6a3885164e3c58e355feb4a7b94176ae127343d (diff) | |
| download | nfs-utils-c0e89b264fb01c5b4bb925b32d1b6b7764c44d4a.tar.gz nfs-utils-c0e89b264fb01c5b4bb925b32d1b6b7764c44d4a.tar.xz nfs-utils-c0e89b264fb01c5b4bb925b32d1b6b7764c44d4a.zip | |
Support for NFSEXP_NOAUTHNLM introduced in 2.3.42
Diffstat (limited to 'utils/exportfs')
| -rw-r--r-- | utils/exportfs/exports.man | 31 |
1 files changed, 30 insertions, 1 deletions
diff --git a/utils/exportfs/exports.man b/utils/exportfs/exports.man index b256e4f..120ed2c 100644 --- a/utils/exportfs/exports.man +++ b/utils/exportfs/exports.man @@ -8,7 +8,7 @@ exports \- NFS file systems being exported (for Kernel based NFS) The file .I /etc/exports serves as the access control list for file systems which may be -exported to NFS clients. It it used by +exported to NFS clients. It is used by .IR exportfs (8) to give information to .IR mountd (8) @@ -124,6 +124,13 @@ However, some NFS clients do not cope well with this situation as, for instance, it is then possible for two files in the one apparent filesystem to have the same inode number. +The +.I nohide +option is currently only effective on +.I "single host +exports. It does not work reliably with netgroup, subnet, or wildcard +exports. + This option can be very useful in some situations, but it should be used with due care, and only after confirming that the client system copes with the situation effectively. @@ -164,6 +171,28 @@ exported with subtree checks enabled. The default of having subtree checks enabled, can be explicitly requested with .IR subtree_check . + +.TP +.IR insecure_locks +.TP +.IR no_auth_nlm +This option (the two names are synonymous) tells the NFS server not to require authentication of +locking requests (i.e. requests which use the NLM protocol). Normally +the NFS server will require a lock request to hold a credential for a +user who has read access to the file. With this flag no access checks +will be performed. + +Early NFS client implementations did not send credentials with lock +requests, and many current NFS clients still exist which are based on +the old implementations. Use this flag if you find that you can only +lock files which are world readable. + +The default behaviour of requiring authentication for NLM requests can +be explicitly requested with either of the synonymous +.IR auth_nlm , +or +.IR secure_locks . + '''.TP '''.I noaccess '''This makes everything below the directory inaccessible for the named |