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

 

 

gLite 3.1

glite-LFC_oracle - Update to version 3.1.3-0


Date 24.01.08
Priority Normal

Description


The gLite LFC service has been updated to the version 1.6.8-1, which introduces new bulk methods for lfc_getreplicasl and lfc_delreplicas. Test results for different methods and bulk/non-bulk operations can be found here:

https://twiki.cern.ch/twiki/bin/view/LCG/LFCBM

It is worth mentioning that the man page for lfc_getreplicasl is missing. However, the next release will contain it. Please, see the related bug:

https://savannah.cern.ch/bugs/?func=detailitem&item_id=32818


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
 #29511 Add a command line tool to list virtual uids and gids defined
 #30234 lfc-modifyusrmap returns "Internal Error" - unique constraint violated
 #31697 LFC daemon crashes with incorrect command from client
 #31976 [LFC] "-n" option missing from init.d and sysconfig files
 #31981 [LFC] Internal error when using lfc-enterusermap (1.6.7-1)

Updated rpms

Name Version Full RPM name Description
LFC-client 1.6.8-1sec.slc4 LFC-client-1.6.8-1sec.slc4.i386.rpm Client side libraries for the LFC
LFC-interfaces 1.6.8-1sec.slc4 LFC-interfaces-1.6.8-1sec.slc4.i386.rpm LCG File Catalog Interfaces
LFC-server-oracle 1.6.8-1sec.slc4 LFC-server-oracle-1.6.8-1sec.slc4.i386.rpm LFC Server for an Oracle database backend
glite-LFC_oracle 3.1.3-0 glite-LFC_oracle-3.1.3-0.i386.rpm Metapackage for the glite-LFC_oracle
glite-yaim-lfc 4.0.0-11 glite-yaim-lfc-4.0.0-11.noarch.rpm glite-yaim-lfc module configures 3.0 LFC.
lcg-dm-common 1.6.8-1sec.slc4 lcg-dm-common-1.6.8-1sec.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)