gLite > gLite 3.1 > glite-TORQUE_client > Update to glite-TORQUE_client 3.1.1-0  
 
 

 

 

gLite 3.1

glite-TORQUE_client - Update to version 3.1.1-0


Date 14.12.07
Priority Normal

Description



This update to glite-TORQUE_client introduces the next version of the glite-yaim-core 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
 #25620 glite 3.1.0 WNs env is missing many grid related envs on SLC4
 #25847 cleanup-grid-accounts.conf empty after reconfiguration
 #26859 Yaim functions require VO__STORAGE_DIR
 #27817 Yaim does not set VO_<VONAME>_* variables for DNS-style VOs
 #28059 Users edginfo, edguser and rgma are not added to infosys group if this group already exists
 #28550 bad lcmaps rules if VO name is prefix of another
 #29356 MON + SE not allowed by YAIM
 #29589 Remove YUM installation support from YAIM
 #29681 Defauld vomses configuration does not allow the creation of rfc-style voms proxy
 #29764 NODE_TYPE_LIST and defaults/*.pre
 #29906 There is a vulnerability in the VOMS server configuration
 #30037 grid_env.sh corrupts MANPATH
 #30056 Incomplete rollback of JPWG patch
 #30153 Spelling Error in config_bdii_only
 #30603 config_rgma_client assumed profile.d directory is there.
 #30848 YAIM -> Modify configure_node to take into account the cream CE
 #30998 YAIM must define GT_PROXY_MODE=old in config_globus_clients
 #30999 YAIM > -r option should also run the _check functions.
 #31008 Default value for MY_DOMAIN
 #31059 [ YAIM ] bug in grid-env-funcs.sh
 #31079 Enable service level for gridftp daemon
 #31160 [YAIM] Modify configure_node to take into account MPI
 #31267 [YAIM] config_gip_service_release contains a typo

Updated rpms

Name Version Full RPM name Description
glite-TORQUE_client 3.1.1-0 glite-TORQUE_client-3.1.1-0.noarch.rpm Metapackage for the glite-TORQUE_client
glite-yaim-core 4.0.3-6 glite-yaim-core-4.0.3-6.noarch.rpm glite-yaim-core

The RPMs can be updated using yum via

Service reconfiguration after update

Not needed.

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)