> The real trick is that I believe these groupings are designed to be something > you can setup on login and then not be able to switch out of. Which means > we can't use sessions and process groups as the grouping entities as those > have different semantics. Not always on login. For big administered systems, we use batch schedulers to manage the placement of multiple jobs, submitted to a run queue by users, onto the available compute resources. But I agree with your conclusion - the existing task grouping mechanisms, while useful for some purposes, don't meet the need here. -- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@xxxxxxx> 1.925.600.0401 _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxx https://lists.osdl.org/mailman/listinfo/containers