----- Original Message ----- > On 02/04/2014 11:20 AM, J. Bruce Fields wrote: > > On Tue, Feb 04, 2014 at 09:34:52AM +1100, NeilBrown wrote: > >> On Mon, 03 Feb 2014 16:01:21 -0500 Steve Dickson <SteveD@xxxxxxxxxx> > >> wrote: > >>> Also how does gss-proxy come to play in all this? Maybe we > >>> just use gss-proxy by default and retire rpc.svcgssd. > >> > >> I haven't really be following and so am only dimly aware of gss-proxy. > >> It's a replacement for rpc.svcgssd - right? > >> So we should get it to start in the same circumstances as rpc.svcgssd? > >> > >> Is there some easy test - eg something existing in the filesystem - that > >> we > >> could use to see if the kernel supports gss-proxy ? > > > > There's a /proc/net/rpc/use-gss-proxy file. > hmm... I forget... who set this... gssproxy daemon? If gss-proxy is configured to provide the kernel nfsd socket (it does by default) then it writes to it at startup. -- 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
