gLite > gLite 3.1 > lcg-CE > Update to lcg-CE 3.1.5-0  
 
 

 

 

gLite 3.1

lcg-CE - Update to version 3.1.5-0


Date 21.02.08
Priority Normal

Description


New version of globus-gridftp startup script to fix bugs 30862 and 32164 affecting only the lcg-CE service.

This release updates the glite-info-provider-ldap package to version 1.1.0 with various improvements:

  • Try put tmp dir under $GLITE_LOCATION_VAR or $GLITE_LOCATION/var.
  • Read LDIF files directly from disk, not through a pipe.
  • Read each LDIF record in one go, not line by line.
  • More efficient matching and substitutions.
  • Do not sort the entries, as it is not needed for "slapadd".
  • Fix for GGUS ticket https://gus.fzk.de/ws/ticket_info.php?ticket=31476.

In addition there is a glite-yaim-core update, which however provides no change for this particular component.

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
 #22970 CPU totals not configurable in YAIM
 #30862 globus-gridftp startup script must configure logging
 #32164 /etc/init.d/globus-gridftp vs. umask
 #32786 config_lcgenv doesn't setup MYPROXY_SERVER
 #33018 [ YAIM ] config_gip_service_release should check whether the info provider file exists
 #33230 [ YAIM ] GLITE_LOCATION_VAR should be used in config_gip_only
 #33271 yaim configuration for 64bit Worker Node

Updated rpms

Name Version Full RPM name Description
glite-info-provider-ldap 1.1.0-1 glite-info-provider-ldap-1.1.0-1.noarch.rpm glite-info-provider-ldap
glite-initscript-globus-gridftp 1.0.2-1 glite-initscript-globus-gridftp-1.0.2-1.noarch.rpm glite-initscript-globus-gridftp
glite-yaim-core 4.0.3-13 glite-yaim-core-4.0.3-13.noarch.rpm glite-yaim-core
lcg-CE 3.1.5-0 lcg-CE-3.1.5-0.i386.rpm gLite metapackage (lcg-CE)

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)