Hi Santanu,
> >> And also, ther is no "unset" in the site-info.def. I noticed that if I
> >> change the "VO_GRIDPP_VOMS_CA_DN"for gridpp only to "VOMS_CA_DN",
> >> keeping res of the CERN VOMS server VOs unchanged (i.e.
> >> VO_ATLAS_VOMS_CA_DN) in the site-info.def, WN configuration works
> >>
> >
> > That is unexpected and wrong.
> >
>
> Sorry I didn't understand - what is unexpected and wrong? The way it
> worked after changing the "VOMS_CA_DN" line for gridpp in the site-info?
Indeed: the code should have kept complaining that VO_GRIDPP_VOMS_CA_DN
was not defined. To debug this further you could run YAIM as follows:
bash -x /opt/glite/yaim/bin/yaim -r -s your-site-info.def \
-f config_vomsdir 2> /tmp/yaim-debug.log
Then look into that logfile to see what happens for the "gridpp" VO.
> >> but I still get:
> >>
> >> /opt/glite/yaim/functions/utils/run: line 59: config_users_check: command not found
> >>
> >
> > That is a worrisome error. The function is defined along with config_users()
> > and should therefore be known at all times. These observations suggest the
> > shell executing the YAIM configuration is running into something weird.
> > Are there any tell-tale signs in /opt/glite/yaim/log/yaimlog?
> >
> >
> Don't worry about that - it was my fault. I have rewritten my own
> config_users() and I made a silly mistake in there. This is okay now.
OK, I should have thought of a local function...
FYI, YAIM 4 also supports pre- and post-configuration steps, which allow the
admin to add or modify things before or after the standard function is run:
https://twiki.cern.ch/twiki/bin/view/LCG/YaimGuide400#Use_local_functions
|