gLite 3.1
glite-WN - Update to version 3.1.3-0
|
Date |
18.01.08 |
Priority |
Normal |
Description
GFAL/lcg_util
This update contains new versions of the GFAL (1.10.6) and lcg_util (1.6.5) components with
bug fixes and new features as follows:
glite-data-gfal v1.10.6-1 2007-12-07
- Fix bug #32016: [lcg-utils] Segmentation fault on lcg-cr with Classic SEs
- Disable --nobdii for Classic SEs
- Fix behaviour of turlfromsfn (error detection)
- Fix bug #15960: lcg-utils should take the VO name from the VOMS proxy
(new dependency to VOMS API)
- Add support to several BDII hosts with fail-over mechanism
- Fix bug #14802: GFAL should use new LFC methods getlinks/getreplicas
glite-data-dm-util v1.6.5-1 2007-12-07
- Fix bug #32016: [lcg-utils] Segmentation fault on lcg-cr with Classic SEs
- Fix lcg-del for Classic SE
glite-yaim
The new version of glite-yaim-clients (4.0.2-4) contains the following changes:
Bug fixes:
- Fix for bug #30200 : correct definition of X509_USER_PROXY variable.
- Fix for bug #28021 : sw dir permissions and ownership.
- Fix for bug #31266 : X509_USER_PROXY is only defined for the UI and not for the VOBOX.
- Fix for bug #31358 : No more leftover files in the TAR_UI
config_java:
- The function config_java has been removed from the function list of all the 3.1 client nodes.
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 |
#14802 |
GFAL should use new LFC methods getlinks/getreplicas |
#15960 |
lcg-utils should take the VO name from the VOMS proxy |
#28021 |
in yaim-3.1.1 config_sw_dir creates new sw dir with root ownership |
#30200 |
New config_lcgenv configures X509_USER_PROXY wrongly |
#31266 |
[YAIM] X509_USER_PROXY should only be defined for the UI and not for the VOBOX |
#31358 |
UI_TAR -- leftover files from previous configuration by another user |
#32016 |
[lcg-utils] Segmentation fault on lcg-cr with Classic SEs |
Updated rpms
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
- Update the RPMs (see above)
- Update configuration (see above)
- Restart the service if necessary (see above)
|
|