Guys, feel free to mail me. It's a pure luck that I read this mail... Yes, different exports for containers definitelly were working in past. And, actually, it's not that easy to break this functionaly since there are not special code parts to support sucn exports in containers. Пользователь "J. Bruce Fields" <bfields@xxxxxxxxxxxx> писал: On Fri, Oct 25, 2013 at 11:18:03AM -0400, Steve Dickson wrote: > On 25/10/13 10:20, J. Bruce Fields wrote: > >> I ideally it would be best not to have mountd at all on NFSv4-only server. > >> > Basically, have the kernel get its exports like it gets it ID mappings. > >> > Until that day comes, which I hope fill be soon, the TCP listener > >> > only effects v3 mounts and we definitely want people to use TCP > >> > with v3. > > I'm not sure if we want to do that, but note one thing we'll need to do > > before then is solve the namespace problems. (We don't currently have a > > good way to run the usermode helper in the right container.) > > Sorry for not keeping up on the container work and possibly asking > dumb question... but there can be different exports per container? Yes, definitely. > I thought it was just different IPs per container.... > > If so, how does that work today? It should work (except possibly for state recovery). I haven't tested it yet, though I hope to. Stanislav has. --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 -- 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
