gLite 3.1
glite-UI - Update to version 3.1.35-0
|
Date |
15.07.2009 |
Priority |
Normal |
Description
glite-UI, glite-WN, glite-VOBOX
New release of yaim clients
Summary of bug fixes:
- VOBOX service provider correctly publishes the supported VOs.
- FTS endpoint can be now specified by the user.
New site-info.def variables
- GLITE_LOCAL_CUSTOMISATION_DIR: This is an optional variable to define a scratch area for pool accounts via EDG_WL_SCRATCH.
For more information please check
glite-WN-3.0.15-3 Update
- GLITE_SD_PLUGIN: Service discovery settings to determine the FTS endpoint. Possible values are:
1) file : look for the FTS endpoint in a static file specified in GLITE_SD_SERVICES_XML.
2) bdii : look for the FTS endpoint dynamically from the BDII. Both options can be specified. The first one is tried first. Default is "file,bdii".
- GLITE_SD_SERVICES_XML: Location of the FTS services.xml cache file. This has to be used in combination with
GLITE_SD_PLUGIN="file,bdii". Default is "${INSTALL_ROOT}/glite/etc/services.xml".
glite-SE_dpm_mysql, glite-SE_dpm_disk, glite-FTA_oracle, glite-FTS_oracle, glite-WN, glite-UI, glite-VOBOX
New version of DPM
- DPM gridftp v1.7.1-2: saves the calculated checksum (via gridftp CKSM) to the name server, e.g. for later reporting via srmLs.
The dpm-gridftp is able to calculate Adler32, Crc32 and MD5 checksums.
- Improved the error reporting of 'dpm-drain'.
- Clear the saved namespace checksum, if file as changed.
- Using libvomsapi, instead of the deprecated libvomsc.
- Avoiding /etc/services for rfio port lookup (wrong value).
- rfio bugfixes and improvements
- The DPM/LFC sources, configuration and init scripts have been improved for portability to SL5, Debian, OS X and Solaris.
glite-LFC_mysql, glite-LFC_oracle, glite-WN, glite-UI, glite-VOBOX
New version of LFC
- The LFC sources, configuration and init scripts have been improved for portability to SL5, Debian, OS X and Solaris.
- Two new methods have been added to the LFC server and the API: lfc_delreplicasbysfn() and lfc_registerfiles(), for the bulk removal or addition of entries.
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 |
#33062 |
DPM build errors due to %typedef deprecation in swig under RHEL5 derivatives |
#36383 |
RFE : dpm-updatespace should allow to change gid |
#40553 |
[DPM]: dpm-drain should replicate non expired volatile files |
#43128 |
[DPM]: Avoid looking up "dpm" service for finding port number |
#43334 |
The non-redhat fallbacks in the service start-up scripts are not working |
#43382 |
rfio_lseek64 can leave file offsets in an inconsistent state |
#44448 |
DPM GIP configuration causing rejected entries. |
#45422 |
dpm.i to dpm_wrap.c creation using swig-1.3.29-2.1 results in errors |
#45565 |
[ yaim-clients] YAIM config_wn function should use GLITE_LOCAL_CUSTOMIZATION_DIR |
#45812 |
DPM memory leak |
#45814 |
DPM: information provider can incorrectly report space token usage as 0 |
#45891 |
DPM/LFC: Use vomsapi rather than vomsc |
#45892 |
LFC/DPM: Can process incomplete request from network |
#46146 |
[ yaim-clients] Wrong default FTS endpoint when configuring UI via YAIM |
#46282 |
DPM: Change configuration to not start srmv2 by default |
#47668 |
[ yaim-clients ] Service provider for VOBOX doesn't publish the supported VOs |
#48767 |
[ yaim-clients ] Problems with glite-wms-* command and finding endpoints |
#48991 |
[ yaim-core ] needed to change config_edgusers |
#49369 |
dpm-listspaces does not honour DPNS_BASEDIR |
#49398 |
LFC/DPM: DPM-interfaces 1.7.1-1 & LFC-interfaces-1.7.2-1 postinstall script upgrade problem |
#49603 |
DPM: dpm-gsiftp logs swapped in DPM-DSI 1.7.1-1 |
#51148 |
[ yaim-clients ] voms-admin needs /opt/ZSI/lib/.../site-packages/ in PYTHONPATH |
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)
|
|