From: Adam Dickmeiss Date: Thu, 14 Aug 2014 13:02:31 +0000 (+0200) Subject: Version 1.5.9 X-Git-Tag: v1.5.9 X-Git-Url: http://git.indexdata.com/?p=metaproxy-moved-to-github.git;a=commitdiff_plain;h=6197dde3460806f66adbd49055754d8bf50cb8c3 Version 1.5.9 --- diff --git a/IDMETA b/IDMETA index 3eb4503..01846a3 100644 --- a/IDMETA +++ b/IDMETA @@ -1,4 +1,4 @@ DEBIAN_DIST="jessie wheezy squeeze" UBUNTU_DIST="trusty saucy raring quantal precise" CENTOS_DIST="centos5 centos6" -VERSION=1.5.8 +VERSION=1.5.9 diff --git a/NEWS b/NEWS index 6fab707..0d0ea95 100644 --- a/NEWS +++ b/NEWS @@ -1,4 +1,13 @@ ---- 1.5.8 2014/07/15 +--- 1.5.9 2014/08/15 + +zoom: make retry on failure configurable MP-565 +The default and existing behavior is that backend failures (any +diagnostic) makes the module re-search once. The behavior may +be changed by db parameter 'retry'. If given value '0' disables +retry and '1' enables it. If not given, the Torus record may +specify with element retryOnFailure (value '0'/'1'). + +--- 1.5.8 2014/08/01 Fix race condition in SIGTERM handling. Could terminate whole metaproxy instead of just a child process. Extremely rare in real life, hit me with diff --git a/win/makefile b/win/makefile index dc24723..81adc12 100644 --- a/win/makefile +++ b/win/makefile @@ -8,7 +8,7 @@ DEBUG=0 # 0 for release, 1 for debug # Metaproxy version -VERSION=1.5.7 +VERSION=1.5.9 # YAZ and YAZ++ directories YAZ_DIR=..\..\yaz