On Oct 29, 2013, at 12:30 PM, Chuck Lever <chuck.lever@xxxxxxxxxx> wrote: > > On Oct 29, 2013, at 12:27 PM, Weston Andros Adamson <dros@xxxxxxxxxx> wrote: > >> The client now supports multiple sec= options as a colon delimited list. >> >> Signed-off-by: Weston Andros Adamson <dros@xxxxxxxxxx> >> --- >> utils/mount/nfs.man | 7 ++++--- >> 1 file changed, 4 insertions(+), 3 deletions(-) >> >> diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man >> index 2a42b93..17b8d88 100644 >> --- a/utils/mount/nfs.man >> +++ b/utils/mount/nfs.man >> @@ -380,9 +380,10 @@ If a value of zero is specified, the >> .BR mount (8) >> command exits immediately after the first failure. >> .TP 1.5i >> -.BI sec= flavor >> -The security flavor to use for accessing files on this mount point. >> -If the server does not support this flavor, the mount operation fails. >> +.BI sec= flavors >> +A colon-delimited list of security flavors to use for accessing files on >> +this mount point. If the server does not support any of these flavors, >> +the mount operation fails. > > Just a nit: The new text kind of suggests that the colons are required. "sec=single flavor" is also still supported. Typically man page language is careful to show both. Good point. Should there be separate sections or should we do something like: sec=flavor(s) The security flavor or flavors to use for accessing files on this mount point. Multiple security flavors may be specified as a colon-delimited list. If the server does not support any of these flavors the mount operation fails. ... -dros > > >> If >> .B sec= >> is not specified, the client attempts to find >> -- >> 1.8.3.1 (Apple Git-46) >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- > Chuck Lever > chuck[dot]lever[at]oracle[dot]com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
