Chuck Lever: > On Apr 20, 2011, at 5:29 AM, Mi Jinlong wrote: > >> >> Chuck Lever: >>> Hi MJ- >>> >>> On Apr 19, 2011, at 4:33 AM, Mi Jinlong wrote: >>> >>>> At RHEL, if user set port for mountd at /etc/services as >>>> "mount 12345/tcp", mountd should be bind to 12345, but the >>>> latest nfs-utils, mountd get a rand port, not 12345. >>>> >>>> This patch make sure mountd be bind to the port which was set >>>> at /etc/service. >>> I don't think this is documented anywhere. Is there a reason it should work this way? >>> >>> The typical way to set mountd's port is to use a command line option. That's the way it works for all the other RPC daemons. By default the ports are set up at random and registered with rpcbind. That's why clients use rpcbind, and not /etc/services, to find these services. >> I don't have a depth research, agree with you. >> But I got different result when I set port for mountd at /etc/services >> between nfs-utils-1.2.3 and nfs-utils-1.2.2. > > IMO that's unintentional behavior. Could I ask a favor: would you bisect nfs-utils to find out exactly where this started and ended? Hi Chuck, It's after your patch "mountd: Support TI-RPC mountd listener" (commit id:b551b1fd0052de9b8c674b30c39d9f2a1e9d79cc). Before this patch, mountd call rpc_init to create rpc socket, after it, if HAVE_LIBTIRPC is defined, mountd will call nfs_svc_create to create rpc socket, that appears. > >> I just think we should get the same result at new nfs-utils as older. > > Is there a real-world use case for this feature? Why isn't the command line option adequate? > I have a test site which depend on this feature. If this feature indeed unnecessary, I will try to modify my test site. -- ---- thanks Mi Jinlong -- 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
