dCache 1.9.2-5 is a maintenance release.
gPlazma: Default cache lifetime for saml (GUMS) and xacml (GUMS, SCAS) plugins is set to 180 seconds by default. Fixed Java 1.5 compatibility.
SRM: Added space reservation support for local SRM copies, i.e. server side srmCopy requests within the same dCache instance. SRM now correctly handles internal message timeouts. Fixed concurrent updates of shared data structure in the logging code. Removed superfluous DNS lookups. Changed -jdbc-monitoring-log option to -log-request-history-in-db-enabled. Make TCP backlog configurable in srm_setup.env and increased the default value from 10 to 1000.
Chimera: Fix various issues in PNFS-to-Chimera migration tools. Fixed repeated close of database in cleaner. The cacheClass tag is now handled correctly. Fixed foreign key violation. Fixed population of t_strorageinfo table when files are flushed to tape.
PoolManager: Marking a pool as read-only in the pool selection unit now prevents it from being used as a destination for pool to pool transfers.
Pool: Fixed an issue with pools getting disabled on transfer errors. Pools now respect the replicateOnArrival flag (a regression from 1.9.0). Newly created replicas now have a last access time equal to the creation time rather than zero.
dCache script: Avoids use of sed -i for improved Solaris compatibility.
FTP: Adopted de-facto standard for FTP list format.
Caching of authorization plugins which call external services is now on by default. The default dcachesrm-gplazma policy file for release 1.9.2-4 had the lines:
#xacml-vo-mapping-cache-lifetime="0" ... #saml-vo-mapping-cache-lifetime="0"
With this setting, caching is turned off, which could lead to timeouts under heavy load. The new default settings are:
xacml-vo-mapping-cache-lifetime="180" ... saml-vo-mapping-cache-lifetime="180"
The values are in seconds. Caching is not needed for the other plugins because authorization data is held in memory. Configuration files are reread only if they have changed since last accessed.
There are no restrictions on the upgrade order from 1.9.2-4 to 1.9.2-5. Any mix of 1.9.2-4 and 1.9.2-5 is supported. Please consult the upgrade instructions of previous releases for mixing 1.9.2-4 and 1.9.2-5 components with earlier releases.