On 03/03/2015 03:12 PM, Martin Pitt wrote: > Hello all, > > Zbigniew Jędrzejewski-Szmek [2015-03-03 19:08 +0100]: >> Are you sure that all of those nfs daemons do not require >> sockets.target and other stuff provided by basic.target to be ready? > > The corresponding upstart jobs trigger on virtual file systems (/sys, > etc.) and rpcbind, and we've used them for years. Also, NFS does not > yet use socket activation, or talks to other services on sockets > (except for rpcbind), so we don't need sockets.target either. The > other dependencies (some network.target, some nss-lookup.target, etc.) > are already specified explicitly. So I'm quite sure. You are correct. rpcbind is the only service we have that uses socket activation, which I don't think works very well... Just last week I notice if you reboot a vm and the first command you type is rpcinfo -p. That command will time out trying to talk with rpcbind. After the timeout everything works fine... I thought I opened a bz but I can't seem to find it. steved. > > That said, there's of course always a nonzero chance that this breaks > in a case which I haven't tested. In particular, I didn't test > kerberos/gssd, I'd appreciate if someone who has a real-world setup > with that could give this a spin. > > Thanks, > > Martin > -- 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
