On Thu, 2 Jan 2014 16:21:50 -0500 "J. Bruce Fields" <bfields@xxxxxxxxxxxx> wrote: > On Wed, Jan 01, 2014 at 07:28:30AM -0500, Jeff Layton wrote: > > It doesn't make much sense to make reads from this procfile hang. As > > far as I can tell, only gssproxy itself will open this file and it > > never reads from it. Change it to just give the present setting of > > sn->use_gss_proxy without waiting for anything. > > I think my *only* reason for doing this was to give a simple way to wait > for gss-proxy to start (just wait for a read to return). > What wasn't clear to me is what would be doing this read. I'll take it from your comment then that patch #1 is acceptable? > As long as gss-proxy has some way to say "I'm up and running", and as > long as that comes after writing to use-gss-proxy, we're fine. > I'll let Simo confirm that that's what gssproxy does, but yes that is the desired behavior. Typically this is done by ensuring that the parent process when daemon()-izing doesn't exit until everything is ready. If gssproxy does need to be changed for that, we have a library routine now in nfs-utils that does this that you can likely copy (see mydaemon()). -- Jeff Layton <jlayton@xxxxxxxxxx> -- 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
