Messages in this thread | | | Date | Fri, 01 Sep 2006 12:34:52 -0400 | From | Peter Staubach <> | Subject | Re: [NFS] [PATCH 019 of 19] knfsd: Register all RPC programs with portmapper by default |
| |
Chuck Lever wrote: > On 9/1/06, Olaf Kirch <okir@suse.de> wrote: > >> On Fri, Sep 01, 2006 at 11:31:25AM -0400, Chuck Lever wrote: >> >>> I don't like this. The idea that multiple RPC services are listening >>> on the same port is a total hack. What other service might use this >>> besides NFSACL? >>> >> Why do you consider this a hack? I have always felt that librpc requiring >> you to open separate ports for every program you register was a poor >> design. The RPC header contains the program number, and the RPC code >> is fully capable of demuxing incoming requests. So I do not think it is >> a hack at all. >> >> And yes, Solaris NFSACL resides on 2049 too. >> > > I meant "Does Solaris advertise NFSACL on 2049 via the portmapper?"
Yes, the Solaris server registers the NFS_ACL service with the rpcbind daemon. And, the NFS_ACL protocol is defined to use port 2049. Please see nfs_acl.x (/usr/include/rpcsvc/nfs_acl.x) for details.
ps - 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/
| |