gLite 3.1
glite-SE_dpm_disk - Update to version 3.1.10-0
|
Date |
22.04.08 |
Priority |
High |
Description
The new DPM/LFC version provides several new features and
bug fixes, for example:
- fix problem of replication of a zero-length file improve logging of
updatefilestatus method
- DICOM back-end service for DPM
- producing re-buildable source RPMs
- group writable directories when SRM started with umask 0
- DPM-DSI: DPM's gridftp does not allow for ':' in SURL (GGUS ticket #32335)
- support for CKSM (md5 only yet)
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 |
#1441 |
nlinks in name server |
#18836 |
man page of dpns-chown is obsolete |
#30874 |
DPM-httpd breaks logrotate on DPM headnode |
#31028 |
2.1.4.-9 rfiod segfaults |
#31157 |
LFC information provider to be fixed |
#31806 |
Problems in configuring dpm-httpd using function config_DPM_https |
#31866 |
enabling dpm-https disables the other protocols (rfio, gridftp) |
#31976 |
[LFC] "-n" option missing from init.d and sysconfig files |
#31981 |
[LFC] Internal error when using lfc-enterusermap (1.6.7-1) |
#32252 |
gridview not configured on gLite3.1 DPM |
#32378 |
$ORACLE_LOCATION/client/lib is hardcoded for libraries |
#32818 |
no man page on lfc_getreplicasl |
#32978 |
lcg-info-provider-lfc : wrong mds-vo-name |
#32981 |
LFC-server-oracle and LFC-server-mysql rpms do not conflict |
#33066 |
[yaim] LFC and DPM oracle infosystem |
#33191 |
lfc-listusrmap gives Internal Error |
#33769 |
pool free space not updated after filesystem drain/removal |
#33920 |
dpm-drain fails to compile when use KRB5 mechanism |
#33921 |
dpm-qryconf does not compile when KRB5 is activated |
#33923 |
dpm-getspacemd.c doesn't compile when KRB5 is used |
#34664 |
There are some vulnerabilities in the LFC (LCG File Catalogue) |
Updated rpms
The RPMs can be updated using yum via
Service reconfiguration after update
Service must be reconfigured.
Service restart after update
Service must be restarted.
How to apply the fix
- Update the RPMs (see above)
- Update configuration (see above)
- Restart the service if necessary (see above)
|
|