Hi Mario,
> Thanks. Is there some way that I can tell it also to disable pool accounts for a number of users? Currently I was battling why some users fail to be mapped and the reason was that production, priority etc roles for CMS have to be single user accounts, not pool accounts. So the current groups.conf that is this:
>
> "/cms/Role=lcgadmin":::sgm:
> "/cms/Role=production":::prd:
> "/cms/Role=priorityuser":::pri:
> "/cms/Role=hiproduction":::prd:
> "/cms/*"::::
> "/cms"::::
> "/ops/Role=lcgadmin":::sgm:
> "/ops"::::
> "/balticgrid/Role=lcgadmin":bgsgm:1601:sgm:balticgrid
> "/balticgrid":bg:1600::balticgrid
>
>
> produces pool accounts for the sgm, prd, pri users that fails for us. So if I manually go and remove the dot from the front in grid-mapfile and restart pepd the mapping works now, but I'd prefer the configuration to be Yaim safe and it's not currently...
That depends on what you have in your users.conf:
if you define a single account for a given flag,
YAIM will use it for the mapping.
https://twiki.cern.ch/twiki/bin/view/LCG/YaimGuide400#Static_accounts
|