> > > - SECNN4: is env.home necessarily unequal to "/"? Would > > > seem better to do the lookup in a subdirectory just to > > > be certain. > > > > Env.home is the directory you specify on the command line, I think the > > presumption is that it is a writeable file system. Pynfs creates tmp > > and tree directories in home (and maybe some files also?). Guess if / > > was writeable, you could specify /, so yea, maybe it should go into tmp. > > Sounds good. env.home does actually include traversing into tmp, so I will leave this test alone. > > A better test might actually be to do LOOKUP down to home and even > > into tmp, looking for a junction, and then do the > > SECINFO_NO_NAME(parent) on the directory handle just across the > junction if one was found. > > Yeah it'd be nice to check that cross-filesystem case but I don't think it's > necessary (and you still have to deal with the case where a mountpoint's not > found). > > If tests at mountpoints were useful perhaps we could pass in a mountpoint > on the commandline. Or add some sort of export-configuration interface to > the serverhelper script and let pynfs setup exports itself. Yea, that might be something interesting to explore at some point. Frank -- 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
