wiki:manuals/releases/r-1.7.0-35
Last modified 14 years ago Last modified on 04/23/07 18:31:05

Relase notes ( 1.7.0-34 -> 1.7.0-35)

Summary

  • Client now sends by default for srm get and put operations, protocols in a different priority order. The order has changed from {http,dcap,gsiftp} to {gsiftp,dcap,http}
  • Adler32 script has changed to automatically determine the path to the jars
  • Staging bug fix (LHCb : no restore on TURL).
  • access two different accounts with the same kerberos ticket or x509 cert now supported
  • dCap door can now be run in the read only mode
  • Bug fixes to the resilience manger so that 0 byte files will not replicate in an uncontrolled way

Details

SRM server and client protocol selection

dCache SRM used to incorrectly select transfer protocol on basis of its internal priorities, considering the array of protocols sent by the srm client as an unordered set. The latest code (1.7.0-35) is changed to consider the client's protocol list to be ordered and prioritized. Unfortunately this exposed the defect in the current srmcp client, it sends the dcap protocol ahead of the gsiftp protocol in its list. The corresponding client release addresses this. For pre 1.7.0-35 client releases, please specify gsiftp protocol as the first protocol in the list using for example the following option: "-protocols=gsiftp,dcap".

Staging bug fixed

Previous releases didn't stage the file from HSM to disk when the SRM returned a TRUL and the file has not yet been on disk. This is fixed. Details : Previous releases didn't stage the file from HSM to disk when the SRM returned a TRUL and the file has not yet been on disk. This is fixed.

Resilient Manager : 0 byte files will not replicate in an uncontroled way

It eventually happened that 0 byte files have been copied uncontrolled to all available pools. This is now no longer the case.