gLite > gLite 3.2 > glite-SE_dcache_nameserver_chimera > Update to glite-SE_dcache_nameserver_chimera 3.2.2-0.sl5  



gLite 3.2

glite-SE_dcache_nameserver_chimera - Update to version 3.2.2-0.sl5

Date 21.07.2010
Priority Normal


glite-SE_dcache_nameserver_chimera, glite-SE_dcache_srm, glite-SE_dcache_pool, glite-SE_dcache_info

This is the first release of dCache for gLite 3.2

The 1.9.5 series of dCache releases will be supported for the duration of the 2009-2010 LHC run. This release is noticeably faster than previous releases particularly for SRM operations. For this and future releases it is recommended that sites migrate previous PNFS name server installations to the more maintainable Chimera name server.

An incompatibility with the apr rpm from SL5 was detected. If you have dependency problems, please remove it before installing dCache.

Updated rpms

Name Version Full RPM name Description
dcache-server 1.9.5-19 dcache-server-1.9.5-19.noarch.rpm dCache Server
dcacheVoms2Gplasma 0.0.8-0 dcacheVoms2Gplasma-0.0.8-0.noarch.rpm dcacheVoms2Gplasma
fetch-crl 2.7.0-2 fetch-crl-2.7.0-2.noarch.rpm Tool for periodic retrieval of Certificate Revocation Lists
glite-SE_dcache_nameserver_chimera 3.2.2-0.sl5 glite-SE_dcache_nameserver_chimera-3.2.2-0.sl5.x86_64.rpm org.dcache.node.glite-SE_dcache_nameserver_chimera_3_2_0
glite-yaim-core 4.0.12-1 glite-yaim-core-4.0.12-1.noarch.rpm YAIM core package
glite-yaim-dcache 4.0.2-8 glite-yaim-dcache-4.0.2-8.noarch.rpm glite-yaim-dcache module configures 3.0 dcache SE.
postgresql 8.4.1-1PGDG.rhel5 postgresql-8.4.1-1PGDG.rhel5.x86_64.rpm PostgreSQL client programs and libraries.
postgresql-libs 8.4.1-1PGDG.rhel5 postgresql-libs-8.4.1-1PGDG.rhel5.x86_64.rpm The shared libraries required for any PostgreSQL clients.
postgresql-server 8.4.1-1PGDG.rhel5 postgresql-server-8.4.1-1PGDG.rhel5.x86_64.rpm The programs needed to create and run a PostgreSQL server.

The RPMs can be updated using yum via

Service reconfiguration after update

Service must be reconfigured.

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)