On Wed, Jan 06, 2010 at 03:22:55PM -0500, Chuck Lever wrote: > My original idea was that this facility would be a set of smaller unit > tests. Since some of statd/sm-notify is now broken out into libraries, I > think that makes it a little easier to craft targeted tests that don't > require a full-blown statd running to carry out (Of course, that's > speculation; I could be wrong, and Jeff has kindly set up the code for us > to test this theory!). > > The old code has a statd simulator that doesn't require root, and uses > its own RPC program number. It might be reasonable to adopt that > approach instead of using the real statd, for some test cases. Like I say, it might be nice to be able to add even more intrusive tests (e.g. that modify the exports and then test the results over "lo" with the kernel client), so I'm actually happy Jeff says he's not bending over backwards to make the tests unprivileged. > Another way to set this up might be to use a container, or run it under a > lightweight kvm. Sounds ambitious for now. --b. -- 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
