gLite > gLite 3.1 > glite-FTS_oracle > Update to glite-FTS_oracle 3.1.5-0  
 
 

 

 

gLite 3.1

glite-FTS_oracle - Update to version 3.1.5-0


Date 16.08.2008
Priority Normal

Description



glite-BDII
This update of the bdii fixes a critical bug which could potentially cause problems on any node type if the variables BDII_VAR_DIR or BDII_DIR are not set in the configuration file.
In addition the the attributed set_lk_max_locks 2000 has been set in the DB_CONFIG file which is a partial solution to Bug #42727.
Removal of glite-info-plugin-fcr solving bug #40649

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
 #33406 FTS: CLI version string is not reported correctly in verbose option
 #38103 FTA: sane defaults for timeout parameters
 #39492 FTS polls status of get put requests too frequently
 #39538 glite-transfer-channel-set: -k option not setting correct value
 #39539 glite-transfer-channel-set: using -x option results in error
 #39554 FTS: srmcopy channels do not check target directory by default
 #39582 transfer log files not moved to 'failed' folder
 #39867 FTA: sd2cache should not look for non-renewal MyProxy server
 #39880 FTA: channel parameter 'TARGET_DIR_CHECK' has incorrect default
 #39882 FTA: source space token, directory check and first marker timeout parameters not passed correctly to transfer process
 #40064 wrong handling of short command line options
 #42799 bdii: varibles not check before running chown

Updated rpms

Name Version Full RPM name Description
bdii 4.0.1-0 bdii-4.0.1-0.noarch.rpm bdii
glite-FTS_oracle 3.1.5-0 glite-FTS_oracle-3.1.5-0.i386.rpm gLite metapackage (glite-FTS_oracle)
glite-data-transfer-cli 3.4.5-1.slc4 glite-data-transfer-cli-3.4.5-1.slc4.i386.rpm gLite Data
glite-data-transfer-fts 3.4.3-1 glite-data-transfer-fts-3.4.3-1.noarch.rpm gLite Data File Transfer Service (FTS)

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)