gLite > gLite 3.1 > glite-LFC_oracle > Update to glite-LFC_oracle 3.1.27-0  
 
 

 

 

gLite 3.1

glite-LFC_oracle - Update to version 3.1.27-0


Date 15.07.2009
Priority Normal

Description



glite-LFC_mysql, glite-LFC_oracle, glite-WN, glite-UI, glite-VOBOX

New version of LFC
  • The LFC sources, configuration and init scripts have been improved for portability to SL5, Debian, OS X and Solaris.
  • Two new methods have been added to the LFC server and the API: lfc_delreplicasbysfn() and lfc_registerfiles(), for the bulk removal or addition of entries.
glite-LFC_mysql, glite-LFC_oracle

New version of yaim LFC

Update of LFC YAIM configuration scripts to work with LFC 1.7.2-4 and later.

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

This update fixes various bugs. For the full list of bugs, please see list below.

Fixed bugs

Number Description
 #48991 [ yaim-core ] needed to change config_edgusers

Updated rpms

Name Version Full RPM name Description
LFC-client 1.7.2-4sec.slc4 LFC-client-1.7.2-4sec.slc4.i386.rpm Client side libraries for the LFC
LFC-interfaces2 1.7.2-4sec.slc4 LFC-interfaces2-1.7.2-4sec.slc4.i386.rpm LCG File Catalog Interfaces
LFC-interfaces 1.7.2-4sec.slc4 LFC-interfaces-1.7.2-4sec.slc4.i386.rpm LCG File Catalog Interfaces
LFC-server-oracle 1.7.2-4sec.slc4 LFC-server-oracle-1.7.2-4sec.slc4.i386.rpm LFC Server for an Oracle database backend
glite-LFC_oracle 3.1.27-0 glite-LFC_oracle-3.1.27-0.i386.rpm gLite metapackage (glite-LFC_oracle)
glite-security-voms-api-cpp 1.8.12-1.slc4 glite-security-voms-api-cpp-1.8.12-1.slc4.i386.rpm org.glite.security.voms-api-cpp v. 1.8.12.1
glite-yaim-lfc 4.0.3-1 glite-yaim-lfc-4.0.3-1.noarch.rpm glite-yaim-lfc module configures 3.0 LFC.
lcg-dm-common 1.7.2-4sec.slc4 lcg-dm-common-1.7.2-4sec.slc4.i386.rpm LCG Data Management common libraries and man pages.

The RPMs can be updated using yum via

Service reconfiguration after update

Not needed.

Service restart after update

Service must be restarted.

How to apply the fix

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