> -----Original Message----- > From: linux-nfs-owner@xxxxxxxxxxxxxxx [mailto:linux-nfs- > owner@xxxxxxxxxxxxxxx] On Behalf Of Chuck Lever > Sent: Tuesday, October 29, 2013 12:30 PM > To: Weston Andros Adamson > Cc: steved@xxxxxxxxxx; linux-nfs@xxxxxxxxxxxxxxx > Subject: Re: [PATCH] nfs.man: add description of multiple sec= options > > > 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. How about "colon-separated list of one or more security flavours"? That's less ambiguous than "colon-delimited"... Cheers Trond -- 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
