On Tue, Sep 23, 2014 at 08:52:45AM -0400, Simo Sorce wrote: > It will not, but right now gssproxy.service also has: > Requires=proc-fs-nfsd.mount > > I want to drop this one. By the way, I think all you actually want is After=proc-fs-nfsd.mount. You don't actually want to bail out if fs-nfsd.mount fails, in fact you don't care if it's activated at all, all you care about is that *if* it's already activated (because nfsd is), then you want it to start before you. And in fact we could instead replace that with a Before=gssproxy.service in proc-fs-nfsd.mount if you preferred. I don't know how to decide which place it goes, or if it matters. --b. > > > >> 2) Add a After=var-lib-nfs-rpc_pipefs.mount to the > > >> gssproxy.service file since gssproxy could careless about either > > >> rpc.gssd or rpc.svcgssd daemons. All it is looking for is the > > >> sunrpc and auth_rpcgss kernel modules. > > > > > > The correct thing is to add a Before: gssproxy.service to > > > var-lib-nfs-rpc_pipefs.mount IMO. > > Again what happen if gssproxy is not installed? Things will > > still come up successfully? > > Yes, afaik After and Before are just ordering instruction and do not > cause any failure if the units are not present at all, or fail to start. > > There are Want and Require directives for strong relationships. > > Simo. > > -- > Simo Sorce * Red Hat, Inc * New York -- 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
