Configuration issue with the 3.1 Update 45

Description

After introducing the fix for Bug #45887, YAIM has stopped to create /opt/edg/var/info directories. This is a mistake since the version of lcg-tags that will be able to write in the new directory /opt/glite/var/info/<SubClusterUniqueId>/<vo> is released in Patch #2940 that hasn't been certified yet. Old directories need to be supported for a while. The workaround is needed in clean installations or when a new VO is added in the CE. Edit $INSTALL_ROOT/glite/yaim/functions/cofig_gip_vo_tag and add at the end the old code to create the /opt/edg/var/info directory:

    for VO in $VOS; do
        dir=${INSTALL_ROOT}/edg/var/info/$VO
        mkdir -p $dir
		f=$dir/$VO.list
		[ -f $f ] || touch $f
        # work out the sgm user for this VO
        sgmusers=`users_getspecialusers $VO sgm`
        sgmuser=`echo $sgmusers | cut -d " " -f 1`
        vogroup=`users_getvogroup ${VO}`
        sgmgroup=`users_getspecialgroup ${VO} sgm`

	sgmgroup=`id -g -n $sgmuser`
	chown -R ${sgmuser}:${sgmgroup} $dir
        yaimlog DEBUG "$vogroup, $sgmgroup"
        if [ "x$vogroup" = "x$sgmgroup" ]; then
                yaimlog DEBUG "Removing grop writeability of files in $dir, sgm's primary group is equal to pool account's primary group."
		chmod -R go-w $dir 
        else
                yaimlog DEBUG "Adding grop writeability of files in $dir, sgm's primary group is different to pool account's primary group."
		chmod -R ug+rw,o-w $dir 
        fi
    done

Configuration issue with cleanup-grid-accounts

Description

SW manager accounts are configured in some sites with the SW area of the corresponding VO as their home dir. If cleanup- grid-accounts is run against these accounts, VO SW area is basically deleted (files older than the threshold). cleanup-grid-accounts will check the home directory it is processing is not matching a SW area and give up with a warning message in this case.

Configuration issue with the 3.1 Update 16

Description