It's nice if you are LHCb, but .... (X509_VOMS_DIR/X509_VOMSES)

[Daniela Bauer]

Hi All,

The 'new' logic in the bashrc/diracosrc where the script checks if /etc/vomses and /etc/grid-security/vomsdir exist and is not empty does not work for the GridPP DIRAC instance. The reason for this is failry simple:

A non-negligible number of our users work on LHC dominated resources, so these directories exist and contain all the necessary files for the LHC VOs but nothing else (/etc/grid-security/certificates is usually fine as it's not VO specific).

I don't want to ask the users to get their central services to update these directories, these are small experiments with little computing support and we would like to keep this as straight forward as possible.

On the other hand I haven't been able to come up with a clean solution as how to set this depending on DIRAC server. Does anyone have a creative idea ?

(I've set it on the GridPP DIRAC UI on cvmfs, but this is not always available from the users' submit nodes.)

Regards,

Daniela

[Federico Stagni]

Hi Daniela,

this is an interesting one. Are you referring to the content of https://github.com/DIRACGrid/DIRAC/wiki/DIRAC-7.3-(v7r3)#bashrc (which is for server) or to the bashrc that is created by dirac-install and/or the diracosrc that is created for py3 installations?

And since when are you seeing this issue? When did we change it?

If it is dirac-install, we can add another switch to dirac-install, or to dirac-configure.

Cheers,

Federico

--
You received this message because you are subscribed to the Google Groups "diracgrid-forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to diracgrid-for...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/diracgrid-forum/30b6cedb-246e-4861-be36-ece8f15308c3n%40googlegroups.com.

[Daniela Bauer]

Hi Federico,

It's in the client (DIRAC UI). I think it's the fallout from this:

https://github.com/DIRACGrid/management/pull/36

As our users slowly but surely upgrade their UIs and therefore regenerate their bashrcs we see it more and more often. We currently recommend v7r1p45 (py2) to match our server for the client. But the same problem exists for py3 against our v7r2 test server - it's a conceptual problem, so I don't think one size will ever fit all.

Cheers,

Daniela

--

Sent from my guinea pig enhanced living room

-----------------------------------------------------------
daniel...@imperial.ac.uk
HEP Group/Physics Dep
Imperial College
London, SW7 2BW
Tel: Working from home, please use email.
http://www.hep.ph.ic.ac.uk/~dbauer/