gLite > gLite 3.1 > glite-VOBOX > Update to glite-VOBOX 3.1.12-0  
 
 

 

 

gLite 3.1

glite-VOBOX - Update to version 3.1.12-0


Date 29.05.08
Priority Normal

Description


Introducing glite-WMS and glite-LB services has updated a few rpm packages, which also affect certain already released gLite components, namely glite-UI, glite-WN, glite-VOBOX and lcg-CE. However, the newer rpm versions should provide unchanged functionality for these components.


Please also have a look at the list of known issues.

Updated rpms

Name Version Full RPM name Description
glite-VOBOX 3.1.12-0 glite-VOBOX-3.1.12-0.i386.rpm gLite metapackage (glite-VOBOX)
glite-security-lcas-interface 1.3.6-2.slc4 glite-security-lcas-interface-1.3.6-2.slc4.i386.rpm org.glite.security.lcas-interface v. 1.3.6-2
glite-security-lcas-plugins-voms 1.3.4-3.slc4 glite-security-lcas-plugins-voms-1.3.4-3.slc4.i386.rpm org.glite.security.lcas-plugins-voms v. 1.3.4-3
glite-security-lcas 1.3.7-1.slc4 glite-security-lcas-1.3.7-1.slc4.i386.rpm org.glite.security.lcas v. 1.3.7-1
glite-security-lcmaps-plugins-basic 1.3.7-3.slc4 glite-security-lcmaps-plugins-basic-1.3.7-3.slc4.i386.rpm This package provides the timeslot (fabric openings hours), poolaccount selection, localaccount selection, LDAP enforcement and POSIX enforcement (changing the process ownership to the mapped user
glite-security-lcmaps-plugins-voms 1.3.7-3.slc4 glite-security-lcmaps-plugins-voms-1.3.7-3.slc4.i386.rpm This package provides the LCMAPS plugins for specialised VOMS handling: voms_localaccount, voms_localgroup, voms_poolgroup and voms_poolacount. (It is recommended to use the voms_localgroup and voms_poolaccount)
glite-security-lcmaps 1.4.2-1.slc4 glite-security-lcmaps-1.4.2-1.slc4.i386.rpm org.glite.security.lcmaps v. 1.4.2-1
glite-wms-checkpointing 3.1.2-3.slc4 glite-wms-checkpointing-3.1.2-3.slc4.i386.rpm org.glite.wms.checkpointing v. 3.1.2-1

The RPMs can be updated using yum via

Service reconfiguration after update

Not needed.

Service restart after update

Not needed.

How to apply the fix

  1. Update the RPMs (see above)
  2. Update configuration (see above)
  3. Restart the service if necessary (see above)