On Sep 2, 2010, at 7:55 AM, Jeff Layton wrote: > On Thu, 02 Sep 2010 07:29:04 -0400 > Steve Dickson <SteveD@xxxxxxxxxx> wrote: > >> Hey, >> >> On 09/01/2010 05:31 PM, Neil Brown wrote: >>> >>> Hi, >>> I was musing about this and thought I would share my musings - not to be >>> taken too seriously unless they resonate with you. >>> >>> If rpc.nfsd is mounting /proc/fs/nfsd, should it also be starting rpc.statd, >>> which should be running before nfsd is started? >>> Should it 'exportfs -av' too? >>> >>> Should mount.nfs be mounting /var/lib/nfs/rpc_pipefs too? >>> It already runs statd as requimred, which in-turn runs sm-notify, though it >>> is really best to run that much earlier. >>> >>> How far do we really want to go with this "just do the right thing" approach? >> Good point... My original thoughts were just to exit if /proc/fs/nfsd was >> not mounted, which would be the simplest way... But in the name of "things >> just working" I feel having rpc.nfsd trying the mount makes some sense... >> >>> >>> Should "rpc.nfsd" be a replacement for /etc/init.d/nfs-kernel-server or >>> whatever your favourite distro calls it? Or should it just be a tool for >>> managing the nfsd threads? >> No and yes.. >> >> I also see rpc.nfsd becoming the real daemon which will take care of >> all the upcalls from the kernel. Basically ripping out all the upcall code >> out of rpc.mountd and putting it into rpc.nfsd. That way rpc.mountd will >> not have to run in V4-only environments. >> > > That seems like a lot of work for little gain. rpc.nfsd (despite its > 'd' suffix) is currently just a "control program". It does its thing > and then exits. > > If you do the above then it'll have to live as a full-fledged daemon. > Won't we just be trading rpc.mountd for rpc.nfsd at that point? What > would be the benefit? > > If you're concerned about the sockets that mountd listens on, I think > that Chuck had a patch at one point that made it possible to run mountd > as an "upcall-only" daemon for v4-only servers. Neil's patches are now in upstream nfs-utils. You can disable all of the network listeners with command line options on mountd. It's been said that people complain that they don't like running rpc.mountd on NFSv4-only servers. I'm not sure why that's a problem we have to fix with a code change. Better documentation, better automatic configuration detection in the NFS start-up scripts, or simply renaming rpc.mountd could solve this issue without the need for rip-and-replace of well-tested code. -- 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
