> Am 07.12.2015 um 16:50 schrieb William Hay <[email protected]>: > > On Mon, Dec 07, 2015 at 03:20:08PM +0000, Ondrej Valousek wrote: >> SGE can use CGROUPS for this bookkeeping you mentioned, too. It is just a >> different filesystem, so it is quite simple to figure out which process >> belongs to which cgroup. >> To me, when using cgroups, additional GID should not be needed any longer. >> At least per: >> >> http://blogs.scalablelogic.com/2012/05/grid-engine-cgroups-integration.html >> >> Ondrej > I think the cgroups implementation on SoGE differs from the OGS one. > It doesn't do everything the OGS one does. > > Supplementary GIDS are more portable than cgroups and have a natural fit to > the > traditional unix access control model.
Yeah - that's a good point, as SGE was always built for heterogeneous clusters consisting of various OS; and Solaris or FreeBSD nodes could also be a part of it. -- Reuti > While cgroups are probably better > than GIDs for killing jobs. > One thing we do with the additional GID is control access to GPUs by chgrping > them from the prolog. While I believe you can do similar tricks with cgroups > its a little more involved. > > Is the additional GID actually causing you any problems? > > William > _______________________________________________ > SGE-discuss mailing list > [email protected] > https://arc.liv.ac.uk/mailman/listinfo/sge-discuss
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ SGE-discuss mailing list [email protected] https://arc.liv.ac.uk/mailman/listinfo/sge-discuss
