I think a second or two is way too short, but I do wonder if it can't issue the unregisters asynchronously, and in parallel. Then it can wait for them all, with a timeout maybe on the order of 10 to 15 seconds. A couple of retries while waiting sounds reasonable. Making the wait interruptible seems dicey. Once the deregistration is started, it seems like it should always make a best attempt to complete it. Also, nfsd is usually started as a service, so there's not likely to be a user. Tom. At 12:38 PM 4/4/2008, Chuck Lever wrote: >Registering a local RPC service has a long timeout. > >When starting the NFSD service, for example, the RPC server wants to >unregister at least 6 different RPC services (three versions of NFS >and three versions of lockd) before it even tries to register the >services it's bringing up. > >Usually this isnt' a problem. However, if a portmapper or rpcbind >daemon isn't running, each one of these registrations causes a long >wait (up to a minute each, I think) while the RPC server attempts to >contact the rpcbind daemon at localhost. > >I don't think this wait is interruptible, either. > >I'm wondering if this long timeout is really necessary. Can we get >by with a second or so, and a couple of retries? -- 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
