Messages in this thread |  | | Date | Fri, 07 Oct 2005 13:26:44 -0400 | | From | Steve Dickson <> | | Subject | Re: [NFS] [PATCH] kNFSD - Allowing rpc.nfsd to setting of the port, transport and version the server will use |
| |
Hey Bruce,
J. Bruce Fields wrote: > > So the obvious question is what will happen if someone does > > rpc.nfsd -N 3 > > on a server supporting 2, 3, and 4. > > It looks like the code in svc_create() will set pg_lovers to 2 and > pg_hivers to 4 in that case. So if someone tries to use version 3, the > error they get back will be a somewhat contradictory "sorry, I only > support versions 2 through 4." hmmm.... good point... But I wonder if this would be better handled in rpc.nfsd process; Similar to what happens when no transports are specified (i.e. both -T and -U flags are set), the server fails to started.
steved. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |