gLite > gLite 3.2 > glite-TORQUE_client > Update to glite-TORQUE_client 3.2.4-0  



gLite 3.2

glite-TORQUE_client - Update to version 3.2.4-0

Date 22.09.2009
Priority Normal


glite-BDII, glite-LFC_mysql, glite-SE_dpm_mysql, glite-TORQUE_client, glite-UI, glite-WN

New yaim core release

New site-info variables
  • UNPRIVELEGED_GRIDMAPFILE per VO: This variable was before defined per site and now it can be configured per VO.
  • USER_HOME_PREFIX per VO: This variable was before defined per site and now it can be configured per VO.
  • EDG_HOME_DIR, EDGINFO_HOME_DIR and BDII_HOME_DIR: The home directories of system accounts can be now be configured. The suggestion is to define them as /var/lib/user_name but YAIM has left the default under /home.
  • GRIDFTP_CONNECTIONS_MAX: It has been increased from 50 to 150.
New functions
config_myproxy_libs: new function to be able to configure the new myproxy server and clients.

Other fixes
Some libraries have been added to LD_LIBRARY_PATH and to be able to configure lcg CE and cream CE in SL5.

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
 #51562 [ yaim-core ] config_lcas_lcmaps_gt4 function does not work on 64-bit platforms
 #51563 [ yaim-core ] config_ldconf function should add /opt/classads/lib[64] path to the configuration
 #52181 [ yaim-core ] LB locallogger doesn't start on sl5_x86_64: missing opt/classads/lib64 in LD_LIBRARY_PATH
 #53143 [ yaim-core ] broken GLOBUS_TCP_PORT_RANGE in gLite 3.2

Updated rpms

Name Version Full RPM name Description
glite-TORQUE_client 3.2.4-0 glite-TORQUE_client-3.2.4-0.x86_64.rpm gLite metapackage (glite-TORQUE_client)
glite-yaim-core 4.0.10-2 glite-yaim-core-4.0.10-2.noarch.rpm YAIM core package

The RPMs can be updated using yum via

Service reconfiguration after update

Service must be reconfigured.

Service restart after update

Not needed.

How to apply the fix

  1. Update the RPMs (see above)
  2. Update configuration (see above)
  3. Restart the service if necessary (see above)