On Thu, 02 Oct 2014 15:27:28 -0400 Steve Dickson <SteveD@xxxxxxxxxx> wrote: > I begrudgingly commit this because when gssproxy is install > the NFS client will *always* start it, which is > a bug in gssproxy... IMHO... If a daemon is not needed > it shouldn't start up... similar to how the gss daemons work. I agree with you that when a service is not needed it should not start, but it is tricky to automatically figure, from init scripts, if it is needed, because gssproxy has is a general purpose tool that can be used for other user-space related uses and not server NFS at all. On the bright side an admin that is annoyed by it being started can simply mask it: # systemctl mask gssproxy.service or even uninstall the package for now. Now the reason gssproxy.service is always started seem to be that although auth-rpcgss-module.service is not going to start and it set to start Before all its Wants ... those Wants seem to be processed and started anyway. I think this may be seen as a bug, we'll probably need to ask upstream if it is or if there is some other clever workaround to Want another unit files conditioned to whether the unit is going to be started at runtime. 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
