Paul M wrote: > Thoughts? Is this a direction we want to go in? As an option, or by default? So ... this proposal adds a 'groups' subdirectory in each cgroup, and places the user generated subgroups in there. It looks like an unnecessary, incompatible and complicating change to me. For example, what would have been cgroup: /mnt/cgroup/user_created_groupname1/user_created_groupname2 now becomes: /mnt/cgroup/cgroups/user_created_groupname1/cgroups/user_created_groupname2 Right? Why would you do this? There is no problem with the current implementation, no bug we're having trouble coding a fix for, no feature we're have trouble adding. The current code, that simply doesn't allow colliding user names because the kernel provided names are already there, works just fine. You're doing this just to "protect the user from themself", to make it more difficult for them to rely on some name that in a future version is no longer available. It annoys users, and rightfully so, to have to permanently deal with interface warts, because the computer is trying to protect the user from some hypothetical scenario that is not a problem the user needs solving. There is really a trivial resolution to this ... stake out what additional kernel generated names might ever be added ... some pattern(s) of characters which all future names will match, which leave wide swaths of names safely available, in perpetuity, for user created names, with no risk of future collision. And did I say incompatible with released versions? Hopefully Paul M isn't too surprised that I'm not endorsing this one ;). -- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@xxxxxxx> 1.940.382.4214 _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers