gLite 3.1
glite-SE_dpm_disk - Update to version 3.1.14-0
|
| Date |
18.08.2008 |
| Priority |
High |
Description
- return space to pool when removing a replica in a space that no longer exists
- disfavour filling filesystems to more than 98 percent of capacity during selection
- added ctrl-c handling and an option to limit total drain size in dpm-drain
- minor bounds checking changes in dpm, ns and Csec
- return a network time out error to client rather than internal error in some circumstances
- apply castor ns fix for bug #31342, for consistency between lcg-dm and castor
- remove popen functionality from rfio
- change in _Csec_recv_token to avoid subsequent double free
- reopen and preserve first 3 file descriptors in rfio_serv.c and Cinitdaemon.c
- consistency fix in rfio_calls.c rfio_call64.c for method of returning from sropen*_v3
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 |
|
#31342 |
Cupv GRP_ADMIN privileges for the stager are not respected |
|
#31385 |
dpm-drain from a UI |
|
#31390 |
dpm drain for volatile files doesn't work properly |
|
#34664 |
There are some vulnerabilities in the LFC (LCG File Catalogue) |
|
#35876 |
dmp-modifypool does not perform syntax cheking |
|
#36556 |
DPM doesn't update the free space correctly when a user tries to put a file which is > size of available space token |
|
#36652 |
dpm-updatespace executed as non-root user resets the space lifetime to the default value |
|
#36706 |
It is possible to update metadata information even if it is a read-only LFC |
|
#36707 |
rfdf no man page, no description |
|
#36849 |
DPM SRMv2.2 crash during srmSetPermission |
|
#37691 |
RFIO preseek/preread fails on repeated blocks. |
|
#38067 |
rfiod segfaults in scan_interfaces() |
|
#38459 |
lfcdaemon 1.6.10-4 can crash or hang |
Updated rpms
The RPMs can be updated using yum via
Service reconfiguration after update
Not needed.
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)
|
|
