gLite > gLite 3.2 > glite-FTM > Update to glite-FTM 3.2.1-2.sl5  



gLite 3.2

glite-FTM - Update to version 3.2.1-2.sl5

Date 21.07.2010
Priority Normal



This is the first release of FTM for gLite 3.2

Updated rpms

Name Version Full RPM name Description
cx_Oracle 5.0.3-1 cx_Oracle-5.0.3-10g-py24-1.x86_64.rpm Python interface to Oracle
glite-FTM 3.2.1-2.sl5 glite-FTM-3.2.1-2.sl5.x86_64.rpm Metapackage for the gLite FTM node
glite-sd2cache 1.0.4-1 glite-sd2cache-1.0.4-1.noarch.rpm Cron to update services.xml file for gLite FTS
glite-service-discovery-api-c 2.2.2-2.sl5 glite-service-discovery-api-c-2.2.2-2.sl5.x86_64.rpm gLite Service Discovery core API and library
glite-service-discovery-bdii-c 2.2.2-3.sl5 glite-service-discovery-bdii-c-2.2.2-3.sl5.x86_64.rpm Command line interface for Service Discovery library.
glite-service-discovery-cli 2.2.1-2.sl5 glite-service-discovery-cli-2.2.1-2.sl5.x86_64.rpm Command line interface for Service Discovery library.
glite-service-discovery-file-c 2.1.2-2.sl5 glite-service-discovery-file-c-2.1.2-2.sl5.x86_64.rpm Command line interface for Service Discovery library.
glite-transfer-monitor-gridview 1.0.3-1 glite-transfer-monitor-gridview-1.0.3-1.noarch.rpm Creates Gridview Input Files from FTS for Gridview Publisher
glite-transfer-monitor-report 1.0.1-2 glite-transfer-monitor-report-1.0.1-2.noarch.rpm Creates FTS Reports Hours, Days or Weeks.
glite-transfer-monitor-schema 1.0.0-1 glite-transfer-monitor-schema-1.0.0-1.noarch.rpm Contains Schema for FTS Reporting.
glite-version 3.2.2-1 glite-version-3.2.2-1.noarch.rpm Shows version information for the installed gLite node types
glite-yaim-core 4.0.12-1 glite-yaim-core-4.0.12-1.noarch.rpm YAIM core package
glite-yaim-fts 4.1.6-1 glite-yaim-fts-4.1.6-1.noarch.rpm glite-yaim-fts configures the gLite File Transfer Service and Agents

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)