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



gLite 3.2

glite-TORQUE_client - Update to version 3.2.2-0

Date 14.06.2009
Priority Normal


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
 #48044 [ yaim-clients ] WN classads are not in the library path
 #48767 [ yaim-clients ] Problems with glite-wms-* command and finding endpoints
 #48806 [glite-wms-job-status] glite-wms-job-status gives an error on SLC5
 #49271 [ yaim-clients ] vdt_globus_essentials packaging change in 1.10.1
 #49436 [ yaim-clients ] PYTHONPATH on SL5 codes python2.3 paths
 #49810 [ yaim-clients ] PERL5LIB env variable is missing perl 5.8.8 libs in SL5 UI/WN TAR
 #50872 [ yaim-core ] rgma client missing TAR UI SL5 x86_64
 #50879 [ yaim-core ] missing lib in TAR UI SL5 x86_64
 #50923 voms-admin failed due to missing glite-UI & TAR UI SLC5 64bit
 #51148 [ yaim-clients ] voms-admin needs /opt/ZSI/lib/.../site-packages/ in PYTHONPATH

Updated rpms

Name Version Full RPM name Description
edg-pbs-utils 1.0.9-2.sl5 edg-pbs-utils-1.0.9-2.sl5.x86_64.rpm edg-pbs-utils
glite-TORQUE_client 3.2.2-0 glite-TORQUE_client-3.2.2-0.x86_64.rpm gLite metapackage (glite-TORQUE_client)
glite-version 3.2.0-0.sl5 glite-version-3.2.0-0.sl5.x86_64.rpm glite-version
glite-yaim-core 4.0.7-10 glite-yaim-core-4.0.7-10.noarch.rpm YAIM core package
torque-client 2.3.0-snap.200801151629.2cri.sl5 torque-client-2.3.0-snap.200801151629.2cri.sl5.x86_64.rpm client part of Torque
torque-mom 2.3.0-snap.200801151629.2cri.sl5 torque-mom-2.3.0-snap.200801151629.2cri.sl5.x86_64.rpm execution part of Torque
torque 2.3.0-snap.200801151629.2cri.sl5 torque-2.3.0-snap.200801151629.2cri.sl5.x86_64.rpm Tera-scale Open-source Resource and QUEue manager

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)